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 2002/02/13 06:30:22 UTC

DO NOT REPLY [Bug 6418] New: - Java Extension class produces different results between Xalan and XSLTC

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

Java Extension class produces different results between Xalan and XSLTC

           Summary: Java Extension class produces different results between
                    Xalan and XSLTC
           Product: XalanJ2
           Version: 2.2.0
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.xsltc
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: tim_elcott@bigfoot.com


When using XSLT I am calling my own Java extension code to return an String 
which is actually nodes to insert into the result DOM (Very nasty  - I know!). 

This works fine when using Xalan 2.2.0 or Saxon 6.5 as the String is converted 
automagically into nodes in my DOM strucuture. When using XSLTC however, the 
result from the Java extension is created as a text node with all the correct 
entity mappings (i.e. < changes to &lt; etc).

I guess this is a bug in XSLTC as the other two support such features.

Cheers,

Tim Elcott