I am working on xsl performance improvement project.The current implementaion uses xalan xslt processor. Original plan is to replace xalan interpretive processor with xsltc ( compile style sheet once and use translets for transform thereon..). It dit not work because current implementaion makes extensive use of xalan:evalaute() library function which is not supported bt xsltc. ANY HELP ..ANY WORK AROUND TO THIS WOULD BE HIGHLY APPRECIATED.. alternately looking at caching Templates objects and use them for transformations. can any one throw some light on Template caching mechanism.
I have around 250 xsl files, will it be wise to cache 250 Templates in JVM memory? Any inputs on this. If some one has sample Template Cache code, please send me for my use.
Originally posted by William Brogden: The first question that occurs to me is what version of Java are you working with? Java 1.5 appears to provide for compiled Templates objects.
In fact Templates has been around since the earliest versions of JAXP. This article is directly relevant to the question.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.