http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2425 *** shadow/2425 Mon Jul 2 16:59:07 2001 --- shadow/2425.tmp.515 Mon Jul 2 16:59:08 2001 *************** *** 0 **** --- 1,27 ---- + +============================================================================+ + | document() method accesses URIResolver multiple times | + +----------------------------------------------------------------------------+ + | Bug #: 2425 Product: XalanJ2 | + | Status: NEW Version: 2.2.x | + | Resolution: Platform: Other | + | Severity: Normal OS/Version: Other | + | Priority: Other Component: org.apache.xalan.transf | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + TestID URIResolverTest.java, URIResolverTest.xsl + Run this test and examine the output (2 Fails generated). Note that the + expected data in the .java file is set to the munged URI's of the three document + () calls when performing the transform(). The LoggingURIResolver however + captures all calls to the URIResolver - and the URI from each document() call + is first resolved twice twice in document order (i.e. a, a, b, b, c, c); then + each one is resolved once again in document order (i.e. a, b, c). One would + think that each URI should only be resolved once. This may have impact on + users who use URIResolvers to define caching or other algorithims. + (Note: I thought I reported this a few weeks back but must have missed it - + this is not new)
