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/21 19:06:07 UTC

DO NOT REPLY [Bug 6620] New: - XSLTC TRAX requires Document nodes for DOMSource

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

XSLTC TRAX requires Document nodes for DOMSource

           Summary: XSLTC TRAX requires Document nodes for DOMSource
           Product: XalanJ2
           Version: 2.3
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.xsltc
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: tim_elcott@bigfoot.com


Unlike Xalan and Saxon the XSLTC TRAX api requires the DOMSource to hold a
Document node which prevents the transformation of an tree fragments. Xalan and
Saxon both work with Element nodes being used within the DOMSource.

There are explicit casts to Document in TransformerImpl.getDom(Source source,
int mask)

Line 412: final Document    tree = (Document)domsrc.getNode();

which, obviously throws a 

java.lang.ClassCastException: org.apache.xerces.dom.DeferredElementImpl

when passing in an Element node.

DOM2SAX also requires an explicit Document node for its constructor.