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

Posted to dev@cocoon.apache.org by bu...@apache.org on 2002/09/05 10:22:25 UTC

DO NOT REPLY [Bug 12328] New: - XSLTProcessorImpl doesn't set new URI resolver to cached templates

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=12328>.
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=12328

XSLTProcessorImpl doesn't set new URI resolver to cached templates

           Summary: XSLTProcessorImpl doesn't set new URI resolver to cached
                    templates
           Product: Cocoon 2
           Version: 2.0.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: general components
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: amir@cti2.com


XSLTProcessorImpl doesn't set the uri resolver for a cached template explicitly 
when .
Since the way the uri resolver is set is not stated clearly by JAXP, some XSLT 
transformers (like SAXON 6.5.2), may use the uri resolver that was used by the 
template the first time (which may not be valid already since it is 
Recylceable). 
This causes a NPE when working with TraxTransformer with caching.

A suggested patch is:

RCS file: /home/cvspublic/xml-
cocoon2/src/java/org/apache/cocoon/components/xslt/XSLTProcessorImpl.java,v
retrieving revision 1.18.2.5
diff -r1.18.2.5 XSLTProcessorImpl.java
290a291
>             handler.getTransformer().setURIResolver(this);

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org