Subj : DOM in XMLLib
To   : netscape.public.mozilla.jseng
From : Jon Brisbin
Date : Tue Sep 06 2005 06:06 pm

How feasible would it be to write a DOM4j-friendly implementation of the 
objects necessary to run E4X in Rhino? This is a huge drawback to me 
using the E4X features in Rhino. If I just had a way to plug in my own 
DOM (and interact with it while my script is running) then I would use 
it hands down. Right now, I'm creating new XML documents in JavaScript, 
then parsing them out from a string and inserting them into a DOM. Not 
very efficient.

I've been looking through the source for the XML stuff and it doesn't 
look like it would be an impossible task, but I'm not sure of the 
ramifications. I only need DOM4J, but it should probably be pluggable. 
I'm not sure I could justify spending extra time writing a pluggable 
architecture for it when I only use DOM4J, but I could probably spend 
some time on a more targeted solution that could be built upon and more 
Xerces (uuuggh!) friendly.

Any E4X gurus around here? :-)

Jon Brisbin
NPC International, Inc.

.