Ian Roberts wrote: > 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
There are a handful of different tree models out there in Java. However, be *very* careful about what you pick and for what reason. JDOM is based on a class hierarchy instead of interfaces so it limits the extensibility and scalability of any application written using it. Once you get past the learning curve for DOM, you may find that you like it. Or not. But either way, make an educated decision. > 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. I wouldn't suggest this because of the memory used to convert between multiple document representations. Your performance will degrade. Pick a model and stick with it. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
