Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

Resin jstl-xslt performance problem

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i have 3 pages:
xml.jsp : produces dynamic xml-data from a database
transform.xsl : xslt-stylesheet
output.jsp : html-output using JSTL
"output.jsp" looks like this:
<%@taglib prefix="c" uri="http://java.sun.com/jstl/core"%>
<%@taglib prefix="x" uri="http://java.sun.com/jstl/xml"%>
<html>
<body>
<c:import url="/xml.jsp" var="xml"/>
<c:import url="/transform.xsl" var="xslt"/>
<x:transform xml="${xml}" xslt="${xslt}"/>
</body>
</html>
the code DOES work with resin but:
everytime i call output.jsp resin triggers a recompile of the page and that is a real performance killer. tomcat does not show this odd behaviour.
i really like resin (excellent performance, easy configuration) so i would not like to be forced to switch to another servlet-engine (=tomcat).
is this a resin issue or my fault???
thanks,
flo
 
Florian Scheichl
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
in case anyone is interested:
i solved the problem by replacing resin's xslt-processor with "xalan" by the apache group. now everything runs just fine.
i have never tested my application with older jsdks - only with 1.4.1, so that might have been an issue, too...
cheers,
flo
reply
    Bookmark Topic Watch Topic
  • New Topic