should we use dom4j in future versions of XMLC?

Have any of the XMLC developers thought about using dom4j ( 
http://www.dom4j.org/ ) in XMLC?  I know the topic of using JDOM has come 
up before and the conclusion was that it doesn't provide anything that DOM 
doesn't already do and forces one into a completely separate interface so 
why change?  Well, dom4j seems to support the existing w3c DOM and multiple 
JAXP compliant XML parsers (including its internal Alfred2 parser) while 
providing a more Java-centric API, better performance, and support for lots 
of different features:

http://www.dom4j.org/index.html#Features

See also....
http://www.dom4j.org/compare.html

The fact that dom4j seems so puggable makes me think that XMLC might 
benefit in both performance and flexibility from using it.  Might this 
solve some of our issues with Xerces and such?  I don't claim to understand 
all the issues involved here.  I just want to get the idea out there and 
see what people like Richard Kunze, David Li, and Mark Diekhans think about 
this ...and, of course, the rest of the XMLC community.

Jake