You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2003/09/10 02:36:49 UTC

DO NOT REPLY [Bug 23048] New: - [XSLTC] URIResolver interferes with XML source

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23048>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23048

[XSLTC] URIResolver interferes with XML source

           Summary: [XSLTC] URIResolver interferes with XML source
           Product: XalanJ2
           Version: 2.5
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Xalan-Xsltc
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: adam@grummen.net


I had some issues implementing my own uriresolver. It had previously worked fine
with xalan interpreted, but gave some unexpected results in xsltc. When I added
the uriresolver to the TransformerFactory and the Transformer, it would find the
correct files called with xsl:import and document(), but it was as if it were
performing the transformation on a blank xml document. If I took out the code
for the uriresolver (and it could find the xsl:imports with the default
uriresolver) it worked fine.