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=22559>. 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=22559 Behaviour of DOMSource(Node) does not match description Summary: Behaviour of DOMSource(Node) does not match description Product: XalanJ2 Version: CurrentCVS Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: org.apache.xalan.processor AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The description of the DOMSource(Node) constructor in the JAXP 1.2 Specification reads as follows: public DOMSource(org.w3c.dom.Node n) Create a new input source with a DOM node. The operation will be applied to the subtree rooted at this node. In XSLT, a “/” pattern still means the root of the tree (not the subtree), and the evaluation of global variables and parameters is done from the root node also. That seems to imply that, given a document like the following, if the Node passed to the DOMSource constructor is the element node named "innermost", the process of building the result tree should begin with the "innermost" element, but that the document node in the XPath data model should correspond to the DOM's Document node, and presumably that the "doc" and "inner" element nodes will be part of the input tree as well. <doc><inner><innermost/></inner></doc> Xalan-Java Interpretive seems to create a DTM that contains a document node containing only the "innermost" element. I'm checking the interpretation with the JAXP Expert Group.
