DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27717>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27717 ------- Additional Comments From [EMAIL PROTECTED] 2008-01-06 22:26 ------- Profiling, all the time is spent in the following line: int ctxtNode = xpathSupport.getDTMHandleFromNode(contextNode); The Javadoc for this method notes that it is non-optimal [wheee]. Reading CachedXPathAPI, what it does is cache the DTMManager, so definitely makes sense that switching back to CachedXPathAPI will fix the slowness of x:out. As there's no JSTL API to modify the DOM, I don't see any reason not to use CachedXPathAPI - except for the memory issue of caching and figuring out where in the lifecycle to remove it. Given that this is only a notable problem for x:out in x:foreach, it would seem that we need to attach the cache to the x:foreach start/close cycle, and have the x:out notice that its session has such a thing. Time to poke around in the code. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
