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:15:30 UTC

DO NOT REPLY [Bug 6417] New: - XSLTC TRAX Implementation produces incorrect DOM structure

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

XSLTC TRAX Implementation produces incorrect DOM structure

           Summary: XSLTC TRAX Implementation produces incorrect DOM
                    structure
           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


XSLTC TRAX API produces a incorrect DOM Structure when using a DOMResult. 

The org.apache.xalan.xsltc.trax.SAX2DOM class automatically adds a Element with 
the name "root" to the top of the DOM tree on the startDocument method. On a 
successful transform call, the node returned from the DOMResult.getNode() 
method is the document node, with this "root" element attached as the first 
child. Xalan and Saxon both have the output document top nodes directly 
attached below the Document node.

Also, as a side issue, the TransformerImpl and SAX2DOM Classes does not respect 
any node already set in the DOMResult.

Tim Elcott