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.
