Originally posted by Gregg Bolinger:
That said I find it hard to believe that anyone doing serious web application development spends time looking at their pages outside of the app server's container.
Agreed, but still it is much simpler to convert an HTML mock up that you used to inspire your customers into a Tapestry template than into a JSP page. Plus, in Tapestry there is simply no way to mix presentation and code.
But these are details. I would say that if the application is simple, there is no difference which framework you choose. But the more complex the application is and the more applications you create, the better the benefits of Tapestry will be seen as you will have to write much less code and you can easily package repeating functionality into your own libraries of custom components.
Alexander Kolesnikov<br />Java Web Developer<br />SCJP 1.4, SCWCD 1.4, SCBCD 1.3<br /><a href="http://sundraw.ws" target="_blank" rel="nofollow">Tapestry 5: Building Web Applications</a><br /><a href="http://sundraw.ws/batik.jsp" target="_blank" rel="nofollow">Java Drawing With Apache Batik</a>