OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Java DOM implementations and cloneNode

[ Lists Home | Date Index | Thread Index ]
  • From: "Don Park" <donpark@quake.net>
  • To: <xml-dev@ic.ac.uk>
  • Date: Tue, 26 Jan 1999 00:02:39 -0800

>Am I expecting too much here? Shouldn't the classes that implement the
>DOM interfaces be able to copy via cloneNode, which is a DOM interface
>function? Is this a bug or expected behavior?

It is not a well known fact that DOM Level 1 does not dictate inter-document
operations or movement of nodes between documents.  You will find that
following is true:

Node node1 = doc1.createElement("boo");
Node node2 = node1.cloneNode(false);
if (node1.getOwnerDocument() == node2.getOwnerDocument())
    System.out.println("both the original and the clone belongs to same

So when you tried to populate the second document with clones of the first
document, you were trying to move nodes from one document to another.

I am quite sure that some DOM implementations allow you do this although it
means your DOM code will no longer work with all DOM implementations.  If
you are willing to stretch your neck just so, you might give the currently
available version 1.0PR3 at www.docuverse.dom/domsdk/ a try.  I am fairly
certain I added code for this.  If not, Docuverse 1.0 Beta 1 definitely will
(soon, real soon now).


Don Park

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS