Spring has web framework, so has Struts.
How is the learning curve for Tapestry
I tried to learn Tapestry 4 in the past but its learning curve and the rareness of the on-line materials were stoppers for me.
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>
Originally posted by Alexander Kolesnikov:
The future is with the component-based frameworks simply because they increase the productivity of development very significantly.
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>
Yeah, I write those. And without a complex framework, component-based or not.I am speaking about complex highly dynamic web applications with sophisticated user interface
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>
Originally posted by Alexander Kolesnikov:
I am speaking about complex highly dynamic web applications with sophisticated user interface,
Originally posted by Sripathi Krishnamurthy:
Based on the comments below, I understand that Tapestry is component based and much easier to use compared to action based framework like Struts.
Struts is known to be very good and has lot of support from Industry. I have personally worked on Spring web framework and found it to be extremely good. Just because a component framework based application is available, should everyone switch to it?
Or does the sheriff's and authors over here define/dictate some kind of thumb rule which would help architects/developers to pin point the exact framework to be used in different circumstances?
For ex, if the web application is rules based use ABC, if the web application is highly complex use XYZ, if the application is simple to medium complex use PQR etc...
I DO understand that every application differs case to case..But one cannot easily adopt sea water being in fresh water..similarly being aware that struts and Spring web framework can solve all the problems, one should have a very strong case to move to a completely different application framework.
This is why I always urge people to get a good handle on Servlet and JSP technology before diving off into a framework. That way, they have the skills they need to decide which, if any, framework suits their own needs.
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>
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |