Welcome to JavaRanch Sue. To start the discussion can you briefly explain about JSTL and the requirments to use the libraries in JSPs. How did you get motivatd to write the book. How different is it from other books out there?
Hi Vasu. JSTL is the JSP Standard Tag Library. It's a collection of frequently used actions that make creating JSPs much easier, more readable, and more maintainable. The Expression Language (EL) was first introduced with the JSTL, but the support of it has now been moved to JSP 2.0. It allows for easy access to objects, and a much cleaner way to deal with presentation data. It should help eliminate the need for using Scriplets in your code. Overall, the JSTL is a technology that most any JSP developer will want to become familiar with and use in their development. You asked what my motivation was for writing the book? If there is a technology that can make a big impact in a developer�s life, I'm usually on it when it comes out. The JSTL was one such technology, so I decided that the practical guide would be a very helpful and useful way to come up to speed very quickly. You'll have to let me know what you think of the book if you get a chance to read it! Sue
Hi SUE Does JSTL make any performance difference? ----------- Sainudheen
Joined: Jul 12, 2001
Thanks for your reply Sue. For a minute I thought you were asking someone else to answer the questions while you are busy with your next book... :-) I have a question about the performance issue of using JSTLs, for that matter any tag libraries. I have a large JSP which I want to split into smaller maintainable JSPs. The original JSP was not using tag libraries. What will be the performance effect of using JSTL? Are there ways to minimise it? Thanks, Vasu
Joined: Apr 21, 2003
Well, I am busy on my next book, but never to busy to answer questions . I feel that the performance issues related to using the JSTL are minimal. If you are adding any code, regardless of what it is, obviously you will have some addition of runtime instructions. However, the additional overhead is not even worth the consideration. Usually there are more pressing issues in an application that can be optimized (such as in business logic) that will get more bang for your buck. What is worth much more is the time spent coding, the amount of debugging required, and the easy of maintenence in your application View files. That is worth more to me and the development teams I work with then 1 ms in saved page execution. my .02 cents! Sue
I agree with Sue that there are better places to look for performance improvements, such as the business logic. I also agree that it is well worth taking a small hit on the performance if this makes the development, debugging, and maintenance of the code easier. Having said that, we did find a significant performance overhead when using JSTL as opposed to scriptlets. This is in JSP pages that are purely concerned with presentation, i.e. there is no business logic on these pages. Because of this, certain parts of our application that need to be highly scalable and performant will be unable to use JSTL for now, while other, less critical parts, can benefit from using JSTL. The reason is most likely the amount of reflection that JSTL uses, which is still an expensive operation. Hopefully, newer versions of Java / JSP, or even more performant implementations of JSTL will get around these initial problems. -Mirko