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:
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
I don't think there's any impediment except for someone's patience.
The Jaxen dependency just came over from XFire.
On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin
sergey.beryoz...@progress.com wrote:
Hi,
javascript component uses it too. But it's the use of Javen within the Aegis
component
The problem here is that Aegis also uses JDOM.
On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin
sergey.beryoz...@progress.com 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
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
2. Try to find a way to avoid using XPath in Aegis (not sure if this
is
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
OK, fellow-sufferers. I've made the basic changes to disconnect Aegis
from JDOM and JAXEN by using XmlSchema directly to construct schemata.
Have we got unit test failures? Oh, my, have we got unit test failures.
I suspect that many of them are cosmetic variations in xml schema
namespace
