OK, then you can create a new document and do a deep clone on all of it's
children, appending them to the new document.
Interesting, I see that cloning of DocumentType, Entity, and Notation nodes
is also implementation-dependent. Doesn't that sort of make the whole
thing implementation-dependent, unless you keep track of what sorts of
nodes are in the tree? What's the purpose of having an interface which
allows cloning, if it requires knowledge of the implementation?
Dave
"Joseph
Kesselman/CAM/Lotu To: [EMAIL PROTECTED]
s" cc: [EMAIL PROTECTED],
(bcc: David N
<joseph_kesselman@ Bertoni/Cambridge/IBM)
us.ibm.com> Subject: RE: DOM_Document
problem...HELP REQUIRED URGENTLY
02/22/2002 08:58
AM
Please respond to
xerces-c-dev
>You can also clone the entire document, which is _much_ easier:
Just for reference: Remember that this won't necesarily work in other DOM
implementations; the DOM Recommendation says clonability of Document nodes
is implementation-dependent.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
