Hi Gary > Import-Package: org.apache.neethi; version="0.0.0"
I checked a CXF bundle manifest, it does import org.apache.neethi using this default version - but why would it cause any issues given that CXF is ok with importing whatever neethi bundle is available there ? DOSGI does ship a neethi bundle. Are you working with a multi-bundle distribution ? Actually, just checked you first post in this thread... So can it be that a neethi bundle has to be installed earlier ? Can you try it please ? Also, you said that a single-bundle distribution was working ok...Interesting. Hopefully you can make it working :-) By the way, can you please attach an Equinox configuration file to the JIRA ? May be we can ship it eventually, or/and may be DOSGI docs will be updated with with some additional advice... thanks, Sergey 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 > > > > Gpinkham wrote: >> >> I haven't tried Felix.. My "boss" picked Equinox and it'll be difficult >> to shake him from it.. :-) He's using extension points and the Equinox >> Servlet Bridge.. We're developing this as an addon to a legacy web >> app.. I heard we could use Ext Points with Felix but haven't tried >> (mostly because of the desire for the bridge and running this under >> Jboss) >> >> I will try to see what I can do with the export on the base OSGi bundle.. >> (need some handy dandy regex to parse out the packages from the logs).. >> >> thanks again, >> Gary >> >> >> Sergey Beryozkin wrote: >>> >>> 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 >>> >> >> > > -- View this message in context: http://www.nabble.com/CXF-DOSGI-%2B-Equinox-Servlet-Bridge-tp24355153p24369297.html Sent from the cxf-user mailing list archive at Nabble.com.
