[jdom-interest] CVS Access to the org.jdom.XPath stuff and another question...

[Jason Hunter]

> I've just finished building from cvs, including the xpath stuff. I'll
> happily send the jar to you if you want to let me know an address to
> send it to. ( 120k )

I sent him one already, plus CVS is up now.

> On this topic, maybe somebody can shed some light on where the XPath
> integration is heading to. Specifically the jaxen stuff. Unless it I'm
> doing something way wrong, it appears that I still need the jaxen jars (
> jaxen-core, jaxen-jdom ) at runtime to use the jdom XPath classes.
> Perhaps somebody can explain why this is better than just using the
> jaxen stuff. Are the jdom classes there purely as a wrapper to the jaxen
> XPath classes?

To provide a standard interface to XPath functionality.  The
implementation is abstracted away.  That way you can depend on XPath
behavior without directly depending on Jaxen.

-jh-