At 09:29 AM 6/24/2003 -0700, you wrote:
I've
not seen the DOM4J UI yet but I'm sure it's superior for Java then the
W3C DOM API.
Certainly superior in that it is a more java-centric approach to the DOM,
but it does provide convesion of native DOM4J-based DOM to W3C DOM and
vice-versa. However, Elliotte Rusty Harold's XOM (
http://www.cafeconleche.org/XOM/
) is supposed to take the best of DOM4J and JDOM and get rid of the bad parts of them. I wonder if XOM wouldn't be the way to go?
The best part is we wouldn't have to battle with the rest of the server over what version of the Xerces parser to use. ;-).
There is no more battle. XMLC's xerces in wrapped in the org.enhydra.apache.xerces package to avoid collisions with other xerces implementations. Essentially, this means that you should be able to use any implementation of the DOM if working with documents outside XMLC. Minimally, you simply need the xml-apis.jar that ships with Xerces2. XMLC will use those and use its internal api rather than any external xerces api.
This is the case now in XMLC's CVS and will be the case when XMLC-2.2 is released.
Jake
| 