Hi, Can you update Equinox to export javax.xml.ws with explicit 2.1.0 version, or starting from 2.0 at least ? Hmm... Personally I'm not sure what to do given that it's a pain for every Equinox user to go and do it, but it also seems like a bit of a risk for CXF to import 0-version apis.
May be CXF (or rather SMX4 or DOSGI) can ship an optional Equinox properties file which can replace the existing Equinox config file, so that users don't have to manually edit the individual package directives ? By the way, how does it all work in Felix ? cheers, Sergey Gpinkham wrote: > > Sorry.. I didn't notice the jiri issue (my search was to tight (used > servletbridge)).. > > I did experiment with setting the system packages property.. I left the > javax.xml.ws package out.. This got me past the "uses" error.. But > produced other errors.. For instance: > > WARNING: Intent map load failed: > org.springframework.beans.factory.parsing.BeanDefinitionParsingException: > Configuration problem: Unable to locate Spring NamespaceHandler for XML > schema namespace [http://cxf.apache.org/policy] > Offending resource: OSGi > resource[classpath:/OSGI-INF/cxf/intents/intent-map.xml|bnd.id=30|bnd.sym=cxf-dosgi-ri-dsw-cxf] > > I'm guessing this is due to me not listing a package in the system > packages property.. (Though the bundles all resolve ok) > > Thanks again > Gary > > > Sergey Beryozkin wrote: >> >> Hi >> >> This JIRA has already been opened : >> >> https://issues.apache.org/jira/browse/CXF-2216 >> >> we've chatted with Dan a bit and it's not quite obvious how to fix it. >> Importing '0.0.0' versions might be a bit risky for CXF, for example, >> multiple jaxws apis may be loaded in a given OSGI container instance. Dan >> reckons some updates might be applied to a maven bundle plugin for it to >> avoid sticking versions to system packages or may be CXF bundle poms can >> have '0' versions hard-coded for such packages. It's still not obvious it >> would be the right approach. >> >> Would it make any sense to have individual Equinox instance properties >> modified instead ? Is there some sort of text configuration file which >> can be edited ? >> >> Any other ideas ? >> >> cheers, Sergey >> >> >> Gpinkham wrote: >>> >>> I'm wondering if anyone else is running CXF under the Servlet Bridge in >>> Equinox?? I ask because of an issue I'm struggling with.. CXF >>> DOSGI comes in two distributions.. One is a single jar which has all >>> it's dependencies inside.. This works fine, but I want to be able to >>> better manage the dependent jars.. >>> >>> So I'm now trying the distribution which has separate jars for CXF and >>> it's dependencies.. >>> When I try this CXF won't resolve.. It has a "Package uses conflict". >>> Specifically Import-Package: javax.xml.ws; version="2.1.0". When I try >>> Packages javax.xml.ws from the console I see the base osgi bundle and >>> the apache service mix bundle (CXF dependency)... It seems that OSGi is >>> exporting java.xml.ws version 0.0.0 and Apache Service mix is exporting >>> javax.xml.ws version 2.1.0... >>> >>> So my question is.. Any idea how to resolve this conflict.. I'm >>> really at a loss.. I saw a blog on the subject that described changing >>> the manifest.. This is only good for things you control.. Not for 3rd >>> party libraries.. I don't want to be modifying the CXF bundles.. >>> >>> Thanks in advance! >>> Gary >>> >> >> > > -- View this message in context: http://www.nabble.com/CXF-DOSGI-%2B-Equinox-Servlet-Bridge-tp24355153p24358286.html Sent from the cxf-user mailing list archive at Nabble.com.
