I'm working with tapestry for 6 months and my main problems were: - The lack of "good" documentation and common problems solutions documentation; - The static structure and dynamic behaviour need.
Sometimes it's painfull when you need to have a reference for the component on the java code, when we want to have two exlusive blocks with the some field inside. 2009/4/29 manuel aldana <ald...@gmx.de> > Inge Solvoll schrieb: > >> 1. What, politically, made it hard to introduce T5 in your organisation? >> Who >> resisted, and why? >> >> > I am sure there a two things which could help at promotion for convincing > decision makers: Real big live sites running under tapestry and a good up to > date book. > > 2. What, technically, made it hard to introduce/teach T5 among your >> programmer colleagues? (some already mentioned documentation) >> > As bigger sites hardly start from scratch, I see the legacy reason as a big > technical point. Usually big codebases rely on action/command focused > frameworks (e.g. struts, spring mvc) and it is extremely hard to refactor > them to page and component based ones. Also I see that frontend people are > being used to work with JSP, freemarker etc. and are a bit hesitating to > look at "yet another" templating technology. > > I really like tapestry concepts and helps a lot to think in different > directions even if you don't use it in daily job. About tap-ioc I really > like to java-code style injection and configuration instead for XML. > > - manuel aldana > ald...@gmx.de > software-engineering blog: http://www.aldana-online.de > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Cumprimentos... Pedro Januário
