Seems JSTL has a stiffer learning curve compared with Struts which already has most of the tag libraries written for one. When would one chose JSTL over struts or in other words is there any advantage of JSTL over struts. Anselm Paulinus
Firstly, I disagree with your premise. I think JSTL is incredibly simple to learn as opposed to a rather large (and obtuse, in my opinion) framework like Struts. The biggest hump in using JSTL effectively is wrapping your mind around the expression language -- which is something you'll need to do anyways since JSP 2.0 is coming and the expression language will feature prominently. Besides, Struts is a complete web application framework. Why use it if all you need are JSP tags? bear
Are you talking about the STRUTS Taglibs? Or STRUTS as an Application Framework. If you are speaking of STRUTS as an Application Framework, I agree with Bear completely. I have been trying to really grasp struts off and on for the last few months, and I still haven't gotten it. So I preceded back to learn JSP/Servlets in detail and when I have a deep understanding of that, maybe STRUTS will click for me more.
There is an overlap in the functionality provided in the current Struts taglibs and the JSTL. The JSTL will more than likely take precedence over the Struts taglibs. In fact, if you find a duplication of functionality between the taglibs and the JSTL, choose the JSTL action. Personally, I feel that it is fairly easy to learn the JSTL and start to immediately see productivity gains. The book is quite straightforward on how to use the actions as well as all of the attributes. The sample code provided should have you up and running in no time. Sue