File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JSTL Performance

 
harold neiper
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are about 30% finished implementing JSTL fmt tablig for internationalization in one of our applications.
Even though I have read plenty of commentary on performance of JSTL I would like to here from others who have implemented the same and what there experience was as it relates to performance.
Also, one of the question brought up recently to me relating to this is how this compares, performance wise, to using jsp includes.
I already understand the benefit of using JSTL over other methods my only concern at the moment is performance.
TIA
Harold
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by harold neiper:
I already understand the benefit of using JSTL over other methods my only concern at the moment is performance.

I'd guess the overhead in the servlet code generated by using JSTL/taglibs is somewhat irrelevant (some event-oriented method calls) when the "normal" JSP code already produces tons of out.println("\r") calls.
However, if anyone has hard facts, I'd be interested to hear about them also.
 
harold neiper
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi David,
Do you have any insight regarding performance gains/hits with using JSTL, specifically the fmt library vs. using jsp includes?
 
David Geary
Author
Ranch Hand
Posts: 45
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by harold neiper:
Hi David,
Do you have any insight regarding performance gains/hits with using JSTL, specifically the fmt library vs. using jsp includes?

First, remember that JSTL is a specification, not a product (unlike Swing, for example). The JSTL reference implementation is fairly slow, but speed was never meant to be its forte. Resin--one of my favorite servlet containers, see www.caucho.com--has a blazingly fast implementation of JSTL.
If you're going to internationalize your apps--and you should if only to encapsulate text presented to the user--using JSTL implementations should give you about the same performance as using Java i18n class like MessageFormat and the like. The JSTL tags, in all likliehood are going to delegate to those classes. (who wants to rewrite all that stuff!)
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic