I forgot one thing! Line-Precise-Error-Reporting !!!!!
The elegent error handling in Tapestry is one of the strongest point. I did not see that in you list. If your developers are like me they sometimes make errors. LPER leads to faster development. Together with live class reloading it's a winner! Cheers! 2012/1/26 Gunnar Eketrapp <gunnar.eketr...@gmail.com> > Clean and readable .... > > Having worked with Spring MVC, JSP, Struts and finally found Tapestry I > can just tell that a web project gets much much more "Clean and Readable" > when choosing T5. > > The elegant page and component folder structure leads to an easy-to-locate > whatever you are searching for. > > It's always hard to win these arguments since people are often suspicious > to new unproven (in their minds) technology. > > If the POC was not enough to convince you manager it was probably not a > god POC or probably not a god manager. > > If you want to be close to the web (html, css, js) I can't think of any > better more robust framework then T5. > > Struts was a mess when I tried it seven years ago but perhaps it has > matured since then (actually T4 was a little bit messy then as well ...) > > I looked at http://struts.apache.org/primer.html and saw that they are > referring to .jsp as key technology. > If there where a minus one button somewhere I would press that one ... > > Gunnar Eketrapp > > 2012/1/26 Thim Anneesens <t.anneess...@ictjob.be> > >> Hello Tapestry users, >> >> The company where I work is going to choose a web framework to implement >> there site (the company core business revolves around that site). We did a >> POC with Spirng MVC, JSF, Struts and Tapestry. >> We have shortlisted to Struts and Tapestry and I have the feeling that >> Struts will win. >> >> The manager decision seams to revolve around the argument that if we can >> do in Struts what we can do with Tapestry while keeping a code that is >> relatively clean and readable, we should use Struts. >> >> *Does anyone have a killer use case that would be difficult to implement >> in Struts and easy in Tapestry.* >> >> I already demonstrated the following about tapestry: >> >> * Better components in Tapestry than in Struts >> * Better persistence tools (FLASH, CLIENT, SESSION ,SESSION STATE, ...) >> * Cleaner templates >> * Less code review because of the framework sensible conventions >> * Better code navigability (when using an IDE) >> * Better refactoring (most of the code is in Java) >> * Coherence and homogeneity (One framework for all your needs / Struts >> needs JSP, Freemarker, Spring services and Tiles to even compete ) >> * Strong Ajax support out of the box >> * Powerful configuration with symbols >> * Beautiful architecture (easy to remember because very sensible) >> * Easy to extend or override most of the features >> * Live class reloading >> * Made with most of the common web use cases in mind (javascript, css, >> ajax, session, query parameters, cookies, integration with backend, >> ...). >> * Everything at your fingertips with Injection and IoC >> >> These are more than sufficient to convince me that productivity and >> maintainability will be far better with Tapestry than with Struts. But >> unfortunately, I fail to demonstrate to the manager :(. >> >> Sorry for my poor English and thanks in advance, >> >> Thim Anneessens. >> > > > > -- > [Hem: 08-715 59 57, Mobil: 070-991 86 42] > Allévägen 2A, 132 42 Saltsjö-Boo > -- [Hem: 08-715 59 57, Mobil: 070-991 86 42] Allévägen 2A, 132 42 Saltsjö-Boo
