copy xml string into a dom tree

[aswin pal]

I have a DOM tree, and a node in it into which I need to copy another XML node.

The general examples advise to load the source as one more DOM tree, do a importNode.

The problem is performance.

I have a huge string (depth-wise) and am looking for alternatives.

Any ideas?

[Paul Clapham]

What exactly were the performance problems which you encountered?

And what exactly are you looking for alternatives to? Do you want to scrap the idea of using a DOM and rewriting the application to handle the XML some other way? Or were you just looking for some other way to import data into an existing DOM?

[aswin pal]

The problem is that I have a DOM tree into which I want to copy XML from a file. That XML content is huge in the number of nodes and their levels.

Loading it into a DOM node and using importNode will be expensive in my case, and I was just trying to see if I can copy that entire thing just as a String into my DOM tree.

Existing DOM tree in code:

<a>
<b>[insert huge XML here]</b>
</a>

XML:

<x>
<y>
<z>
</z>
</y>
</x>

[Anish Kuti]

From your reply it seems .. the problem is huge XML - that memory consumption is high.
You can try using XML bean for this.

[aswin pal]

Thanks. Could you tell the high-level steps.

Download http://xmlbeans.apache.org/ and...

[aswin pal]

Also, a quick read of http://xmlbeans.apache.org/ tells me of it as a java-xml binding api.

My XML is without a schema and all I want is to add huge XML to existing DOM tree without importNode that will parse that content (and therefore consume time).

[William Brogden]

Why are you using DOM at all, why not treat the problem as one of merging two text streams?

If you absolutely need to parse document 1 to find the insertion point, do it with SAX, writing the contents of all events as Strings to a new output file and inserting your new text when you hit the insertion point.

Bill

[aswin pal]

Worked. thanks. was over-engineering and forgot about good old SAX.

[aswin pal]

Also, would passing xml to createTextNode() as a normal string be a bad idea? I have not tried it at the moment...

[Paul Clapham]

aswin pal wrote:Also, would passing xml to createTextNode() as a normal string be a bad idea? I have not tried it at the moment...

It would be a bad idea if you expected the createTextNode method to parse the XML into nodes. It would be a good idea if you wanted the XML to remain as an uninterpreted string, and if you expected the markup (characters like < and >) to be escaped.