Flavio, You may be interested to read through this bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=27717 The release notes for Standard 1.1.1 contain the following in the section "September 2003 • Standard 1.1.0-B1": Our dependency on jaxen and saxpath has been removed by switching our XPath support to Xalan. So, my guess is that returning to Jaxen is unlikely. In fact, I would expect the plan is to move towards standardizing on JAXP 1.3 and the javax.xml.xpath API. As for fixing the performance issue, I believe that can done without reverting to Jaxen, but I haven't spent enough time in that part of the codebase to say for sure. Quoting Flavio Tordini <[EMAIL PROTECTED]>: > hi all, > The performance of the JSTL XML 1.1 tags is really poor. Version 1.0 was much > > faster maybe because it used Jaxen and it cached parsed XPath statements, > while the current Xalan based implementation does not. > Since some of my pages were too slow, I tried to restore the 1.0 code in > XPathUtil.java and managed to recompile. I discovered that the tags are now > 100 TIMES FASTER! A modified XPathUtil and a test JSP are attached. > (I also put a compiled webapp at: > http://purl.org/net/flavio/jstl-test.tar.gz ) > > Basically it's the same XPathUtil from version 1.0.6 but some methods throw > JspTagException instead of SAXPathException. > > What the developers are planning to do about this performance problem? > What are the reasons behind the switch from Jaxen to Xalan? > And finally... Will you accept my patch and go back to Jaxen? > > regards, > Flavio Tordini > > P.S. the patch also fixes bug 30068 > http://issues.apache.org/bugzilla/show_bug.cgi?id=30068 -- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
