jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27717] - <x:forEach> very slow in JSTL 1.1
Date Mon, 07 Jan 2008 06:26:05 GMT
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 bayard@apache.org  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: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org


Mime
View raw message