i'd like to merge two docs ...

[James Todd]

hmmm ... this is pretty much what i did with the exception of
the "removeChild()" step. my interpretation of this is that the
removeChild step will disassociate/null the OwnerDocument
so that it is effectively orphaned and can be added into the
new hosting doc.

i'll give it a whirl.

thx much,

- james

Steve Muench wrote:

> Assuming you have XML DOM Documents "one" and "two"
> and that "oneElement" is the element in doc "one"
> to which you'd like to append the entire content
> of "two"...
>
> You should be able to do:
>
>    Element twoDocElt = two.getDocumentElement();
>    two.removeChild(twoDocElt);
>    oneElement.appendChild(twoDocElt);
>
> _________________________________________________________
> Steve Muench, Consulting Product Manager & XML Evangelist
> Business Components for Java Development Team
> http://technet.oracle.com/tech/java
> http://technet.oracle.com/tech/xml
> ----- Original Message -----
> From: James Todd <jwtodd at pacbell.net>
> To: <xml-dev at ic.ac.uk>
> Sent: Wednesday, December 01, 1999 9:43 PM
> Subject: q: i'd like to merge two docs ...
>
> |
> | hi -
> |
> |     i could use a pointer or two, a recipe if you will, on how best to
> |     "modify and merge" two xml docs. the scenario:
> |
> |         an inbound xml "fragment", a complete xml doc in it's own
> |         right, is amended (eg. one new attribute is added)
> |
> |         the results of which is appended, as a child node, to a
> |         "hosting" xml tree
> |
> |     i've got most of this working using the ProjectX [? Mr. Brownell ?]
> |     parser yet it fails during the appendChild() stating that the child
> | node
> |
> |         "That node doesn't belong in this document"
> |
> |     due to the fact, i believe, that it has a distinct OwnerDocument.
> |
> |     my methodology to date is to create dom's for both the inbound
> |     "fragment" and the destination xml docs afterwhich i'd like to
> | modify
> |     the fragment (hence going the dom route) and finally add the results
> |
> |     to the destination doc via appendChild().
> |
> |     i had hoped to bypass walking the tree in order to create an
> |     "document ownerless" copy with which to work with. is there
> |     a better/preferred means by which to accomplish this task?
> |
> |     any/all comments and suggestions welcomed.
> |
> |     thx much,
> |
> | - james
> |
> |
> | xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
> | Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on
> CD-ROM/ISBN 981-02-3594-1
> | To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
> | unsubscribe xml-dev
> | To subscribe to the digests, mailto:majordomo at ic.ac.uk the following
> message;
> | subscribe xml-dev-digest
> | List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
> |
> |
>
> xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
> To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
> unsubscribe xml-dev
> To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)