It's important to keep a perspective here. So I'll give you mine on the points of that article concerning the disadvatages. Disadvantage: Overhead I highly disagree here. There are ways (like precompiling JSPs) to mitigate this. As other implementations of the JSTL make their way into app servers they will be highly optimized, so I think this point is not really valid Disadvantage: Not as Extensive as JSP Scriptlet I also disagree. I have seen the most horrendous code in JSPs all in the name of Scriplets! 99% of the time the scriplet code is doing some business logic (not presentation logic) and just added a maintenance headache into the application. You have access (very easy access) to objects in the JSTL that make it easier and cleaner to use. Disadvantage: May Seem Burdensome for Experienced Programmers I also disagree here. If you are working with JSPs, you are probably also using custom actions. If you are using custom actions, I know I'd rather learn a full-featured set of actions once, This is usually the case because a different developer wrote yet another iteration tag. I think your productivity goes way up after you've spent a very short time with the JSTL.
I agree with Sue there on the misuse of scriptlets. I have seen a very neat JSP the other day using web method technique( part of the struts architecture). There are really small JSPs which are used only for display and there are tags where the java code goes. The JSP is what a JSP should look like. Unfortunately most of the JSPs that we come across have millions of lines of java code in the scriptles just because scriptlets can contain java code. Vasu
What a wonderful world!
Ko Ko Naing
Joined: Jun 08, 2002
I just would like to share the research that I have found out on the net... If there is no disadvantage on using JSTL, then let's use it!!! I am also eager to learn that technology deeply...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com