Maybe you'd be better off using a different object model. Have you looked at JDOM (http://www.jdom.org)? JDOM nodes can be freely renamed, and manipulated in rather more friendly ways than W3C DOM nodes. JDOM has its own serializer to convert the JDOM tree to XML, or alternatively, you can build a W3C DOM tree from the JDOM one if that suits your purposes better.
Thanks, Ian. I'll look at that next time. I'm pretty much done with my current project, so it'll have to do.
With no disrespect meant to the DOM folks, I have to say that the DOM is cumbersome. And I don't understand how version 1 made it out the door with no way to actually get XML out of the document. XML is all about text, yet the DOM fails utterly to deliver it.
That said, I rewrote all my Xerces C++ - based code in Java in two weeks, starting with no knowledge of Java whatsoever. A lot of that decision was inspired by the fact that you can easily serialize the DOM in the Java version, and you can instantiate an HTTP connection and transmit easily with Java.
I am converted. Aside from some dumb limitations (no operator overloading; no unsigned integers; some more immutable class properties, like the Exception's error message), Java rules!
And the Java community seems quite helpful as well.
Regards, Gavin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
