Re: XPath and Jaxen
Jason Hunter <[email protected]>
| Newsgroups | gmane.comp.java.jdom.general |
|---|---|
| Message-ID | <[email protected]> |
It wasn't really discussed. My guess on why it happened this way is Jaxen was a new project then and decided to provide support for the existing object models rather than ask them to support Jaxen. -jh- On Sep 12, 2011, at 2:45 AM, Rolf wrote: > Indeed, that's the way I see it (and it's also what I am doing to get the testing done. > > It is also what I see as the 'logical' way it should be done, which is also why I am asking... why was it not done that way first time around? > > Rolf > > > On 12/09/2011 1:52 AM, Thomas Scheffler wrote: >> Am 12.09.2011 02:43, schrieb Rolf: >>> What is the right way to do this migration...? >> >> Hi, >> >> as I understand the Jaxen code correctly you have to implement the >> Navigator interface to add support to any library. >> >> I would conclude that you have to move the JDOM-Jaxen-Code completely to >> JDOM. This way there is no circle dependency anymore and no need to fork >> any version of Jaxen here. As JDOM2 is an different library than JDOM >> and you are free to do this. JDOM2 would than depend on Jaxen and that's >> it. >> >> regards, >> >> Thomas >> >> >> _______________________________________________ >> To control your jdom-interest membership: >> http://www.jdom.org/mailman/options/jdom-interest/[email protected] >> > > _______________________________________________ > To control your jdom-interest membership: > http://www.jdom.org/mailman/options/jdom-interest/[email protected] _______________________________________________ To control your jdom-interest membership: http://www.jdom.org/mailman/options/jdom-interest/[email protected]