XOM API for Processing XML with Java

[Elliotte Harold <elharo AT metalab.unc.edu>]

Wolfgang Hoschek wrote:

> I'd appreciate it very much if XOM had no hard dependency on Jaxen. The  
> easy fix below requires no more than 5 minutes of work and makes no  
> changes to the public API at all. Any particular reason that's not  
> being done?

There will be a hard dependency on some XPath engine. Possibly in the 
future that engine will change. I plan to explore SAXON 6.5.3, 
especially if I can figure out how to fix the bugs in its XSLT support 
so I could dump Xalan. But XPath support is only going to get more 
deeply tied into XOM as 1.1 moves forward (i.e. it is likely other 
methods are going to start depending on the correct operation of 
Node.query()), so I'm not inclined to pull Jaxen out unless I've got a 
replacement.

--
Elliotte Rusty Harold  elharo AT metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim