Copy the nodes from one Document obj to another Document Obj.

Question

Hi All,
I have two Document Objects created out of the same InputStream source.Both of them have the same DTD, namely SourceDoc and TargetDoc.
Now when I try to replace a node in TargetDoc with that in SourceDoc, it is giving me the below exception.
*org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node
in a context where it does not exist.*
I then tried with TargetDoc.importNode(), even this function resulted in the same above error. How can I make the Parser get to know that , both the SourceDoc and the TargetDoc belong to the same XSD...
Thanks,
Sabarisri. N

Answer 1

Hi Sabarisri, I have to downplay a bit the drama that might appear in the response above. After looking at my notes, I think if the schema document is properly made (in particular, not itself invalid---that's important), you can normally proceed with in-memory revalidation. That I have renew the checking using a demo, like this.
Let the xsd look like this.
<?xml version="1.0" encoding="UTF-8"?> 
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> 
<xs:element name="root" type="roottype" /> 
<xs:complexType name="roottype"> 
  <xs:sequence>
    <xs:element name="child" type="xs:string" maxOccurs="2"/> 
  </xs:sequence> 
</xs:complexType> 
</xs:schema>This is a correct xsd in itself.
Suppose you've an xml doc like this.
<root>
  <child>child-1</child>
  <child>child-2</child>
</root>If you proceed with append another child to the dom tree and do an in-memory revalidation, it can be done without complication. For this category of problems, you should not encounter the problem I mentioned.
//suppose the doc be the xml document loaded into the dom-tree
//suppose the validator being the Validator instance with the xsd document loaded
//this would lead to no error before doing anything else
validator.validate(new DOMSource(doc));
//then you start make another child to make the doc invalid
Element elem=doc.createElement("child");
elem.setTextContent("child-3");
doc.getDocumentElement().appendChild(elem);
//do an in-memory revalidation, using the same validator in the memory already
validator.validate(new DOMSource(doc));
//this time it will result in error in the error handler of the validator as expected --- normal behaviourFor this kind of re-validation, which belongs to a very large category of problems to encounter, you should be able to do it like the above. (Just bearing in mind, on some fringe cases, oddity might result.) Hence, I should not encourage a temporary intermediate xml file approach, which all can understand very clumnsy and inefficient.