I think I'm seeing an issue in Xerces2 Java that was previously
reported and fixed in XercesC++.
internal subset lost after using cloneNode
http://issues.apache.org/jira/browse/XERCESC-1170
Is this a known problem in Xerces2 Java? The internal subset exists
perfectly intact until I call Document.cloneNode(true). When I
perform a print of the nodes, here's what the document type looks
like, first before the clone (expected) and then after (actual)....
Expected....
DocumentTypeImpl: name=document
internalSubset=
<!ENTITY erh "Elliotte Rusty Harold">
<!ELEMENT document (title, signature)>
<!ELEMENT title (#PCDATA)>
<!ELEMENT copyright (#PCDATA)>
<!ELEMENT email (#PCDATA)>
<!ELEMENT hr EMPTY>
<!ELEMENT lastmodified (#PCDATA)>
<!ELEMENT signature (hr, copyright, email, lastmodified)>
Actual....
DocumentTypeImpl: name=document
EntityImpl: name=erh
TextImpl: Elliotte Rusty Harold
As you can see, Document.cloneNode(true) seems to turn the internal
subset <!ENTITY> into an actual Entity Node and the rest of the
internal subset (the <!ELEMENT>'s) is discarded.
Any ideas about this one?
Jake
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
