There is no issue with the JDOM library though. AFAIK, JDOM has a
pluggable XPath mechanism, but I'm not sure what other implementations
are available for it.
So I guess the options are:
1. Find another XPath handler for JDom
And implement it such that it would delegate to JAXP...?
The other option is to rewrite Aegis to use plain DOM but it can be a major
refactoring
Cheers, Sergey
2. Try to find a way to avoid using XPath in Aegis (not sure if this
is possible at all)
3. Rewrite the XPath processing code to use something else, such as
JAXP as Sergey suggests.
Ideas anyone?
David
2009/1/2 Benson Margulies <[email protected]>:
The problem here is that Aegis also uses JDOM.
On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin
<[email protected]> wrote:
Hi,
javascript component uses it too. But it's the use of Javen within the Aegis
component which is problematic as Aegis databinding is used by DOSGI...
Benson - is there any reason why Java(x) XPath can not be used instead ?
Cheers, Sergey
Hi all,
I noticed that there is a dependency on Jaxen in the Aegis Data
binding (AegisDatabinding.java). This could be a problem for using CXF
by certain communities.
More specifically, the Eclipse community has specifically disapproved
the use of Jaxen. See here:
http://dev.eclipse.org/ipzilla/show_bug.cgi?id=137
So having a Jaxen dependency pretty much makes it not possible for CXF
to be used by an Eclipse project.
Would it be possible to factor this dependency out somehow? I noticed
that it only seems to be used in one place...
Best regards,
David
