Jaxen dependency
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
Re: Jaxen dependency
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
Re: Jaxen dependency
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 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 > >
Re: Jaxen dependency
The problem here is that Aegis also uses JDOM. On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin 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 > >
Re: Jaxen dependency
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 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 : > The problem here is that Aegis also uses JDOM. > > On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin > 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 >> >> >
Re: Jaxen dependency
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 : The problem here is that Aegis also uses JDOM. On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin 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
Re: Jaxen dependency
I've spent the afternoon writing all of the JDOM out of Aegis except for the explicit support for it. This included a complete conversion to XmlSchema instead of direct Schema dom construction. Debugging this will take a while. On Fri, Jan 2, 2009 at 12:15 PM, Sergey Beryozkin wrote: > > >> 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 : >>> >>> The problem here is that Aegis also uses JDOM. >>> >>> On Fri, Jan 2, 2009 at 6:28 AM, Sergey Beryozkin >>> 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 >>> >
Looking for help with Aegis, XmlSchema, no JAXEN
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 prefixes brought on by the changes. I'm a bit overwhelmed by the quantity. If any of you who actually, ahem, get paid to work on CXF would like to see the back of Jaxen sooner rather than later, you could co the following branch and start to help me look at this. https://svn.apache.org/repos/asf/cxf/sandbox/benson/aegis_xmlschema
Much bigger 'uh, oh'
I just did an svn switch followed by an 'svn commit'. So I should have been making changes to my branch. The email that came back seems to be telling me that I just inflicted this on the trunk.
