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/07/09 23:54:17 UTC
DO NOT REPLY [Bug 10616] New: -
copy-of puts invalid content into attributes, comments, PIs
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=10616>.
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=10616
copy-of puts invalid content into attributes, comments, PIs
Summary: copy-of puts invalid content into attributes, comments,
PIs
Product: XalanJ2
Version: 2.4Dx
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Xalan
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: David_Marston@lotus.com
Originally reported to me by David Bertoni.
See test cases copy56 and 58 through 60.
All have a copy-of inside an instruction (xsl:attribute, xsl:comment,
xsl:processing-instruction) that is supposed to have text-only constructors.
Xalan stringifies the whole node-set or RTF instead of taking only top-level
text nodes and discarding the rest.
(If you want to stringify everything, use value-of.)
Possible ambiguity about ignoring offending nodes "and their content" in the
node-set case: <elem>text</elem> as sole item selected