Sorry, missed this email, it appears you solved it, great :-) I'm still a bit confused about that neethi issue though :-) Is it an ordering issue ?
cheers, Sergey Gpinkham wrote: > > Ok so hopefully this solves it.. (so far so good).. I had to add the > version="2.1.0" to two more javax.xml packages in the system.packages > property.. And now CXF starts... I can start my bundle which in turn > registers the Web Service end point with CXF (thru Declarative Services) > and all is good in the world.. :-) > > I will continue to experiment with this.. Its not my idea solution but > it'll have to do for now.. > > Thanks again! > Gary > > PS.. I added version="2.1.0" to the following packages: > javax.xml.namespace;version="2.1.0", > javax.xml.stream;version="2.1.0", > javax.xml.ws;version="2.1.0", > javax.xml.ws.handler;version="2.1.0", > javax.xml.ws.handler.soap;version="2.1.0", > javax.xml.ws.http;version="2.1.0", > javax.xml.ws.soap;version="2.1.0", > javax.xml.ws.spi;version="2.1.0", > javax.xml.ws.wsaddressing;version="2.1.0" > > > Gpinkham wrote: >> >> Ok. So I added every system package to the system packages property in >> the equinox configuration.. And then added version="2.1.0" to all the >> javax.xml.ws packages.. This gets past the "uses" error I previously >> had but introduces a new "uses" error.. >> >> org.osgi.framework.BundleException: The bundle could not be resolved. >> Reason: Package uses conflict: Import-Package: org.apache.neethi; >> version="0.0.0" >> >> Seems like I'm just running in circles with this.. Have been for a week >> now.. :-( >> Gary >> > > -- View this message in context: http://www.nabble.com/CXF-DOSGI-%2B-Equinox-Servlet-Bridge-tp24355153p24369651.html Sent from the cxf-user mailing list archive at Nabble.com.
