amiro 02/02/13 06:52:48
Modified: java/xdocs/sources/xalan xsltc_constraints.xml
Log:
add release note for bug 6417
Revision Changes Path
1.28 +9 -0 xml-xalan/java/xdocs/sources/xalan/xsltc_constraints.xml
Index: xsltc_constraints.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/xsltc_constraints.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- xsltc_constraints.xml 12 Feb 2002 22:47:57 -0000 1.27
+++ xsltc_constraints.xml 13 Feb 2002 14:52:48 -0000 1.28
@@ -78,6 +78,15 @@
after an xsl:comment element. This has been reported to happen only when
the stylesheet also includes
an xsl:for-each element (bugzilla 6109).
</li>
+ <li>XSLTC TRAX API produces an 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, the TransformerImpl and SAX2DOM
Classes does not respect
+ any node already set in the DOMResult (from bugzilla 6417).
+ </li>
</ul>
</s2>
<anchor name="xsltcsmart"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
