(Thim, you don't know what poor English is...) It's always difficult to win these arguments on technical merits alone, especially because they are often looked at one-by-one instead of as a whole. If at all possible, try to find an angle that your organization or your manager deeply cares about. For example, if you had more people with Tapestry experience than Struts people, that'd be a winning argument for me if I was a manager. If you can't find anything else, try this: Struts is a dying architecture, as proven by these graphs: http://markmail.org/search/?q=list%3Aorg.apache.struts.users http://markmail.org/search/?q=list%3Aorg.apache.tapestry.users http://www.google.com/insights/search/#q=%22tapestry%205%22%2C%22apache%20struts%22&cmpt=q
Granted, Tapestry doesn't fare that much better in these comparison but before you doom Tapestry to oblivion, note that many other programming languages, and especially web frameworks based on other languages than Java have been chipping away Java's general popularity: http://www.google.com/insights/search/#q=java%2C&cmpt=q Personally, of those choices, Struts would be the last one I'd pick. Kalle On Thu, Jan 26, 2012 at 12:33 AM, Thim Anneesens <t.anneess...@ictjob.be> wrote: > 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. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
