The more I think about this, the more I'm -1 to this change, or at least -1 until the real underlying problem can be identified and fixed. A JAX-WS application using JAX-WS API's should not be importing a specific JAX-WS implementations SPI.
Dan On Aug 29, 2012, at 2:25 AM, [email protected] wrote: > Author: ffang > Date: Wed Aug 29 06:25:13 2012 > New Revision: 1378451 > > URL: http://svn.apache.org/viewvc?rev=1378451&view=rev > Log: > [CXF-4489]cxf-wsn-api bundle can't find org.apache.cxf.jaxws.spi.ProviderImpl > in OSGi container > > Modified: > cxf/trunk/services/wsn/wsn-api/pom.xml > > Modified: cxf/trunk/services/wsn/wsn-api/pom.xml > URL: > http://svn.apache.org/viewvc/cxf/trunk/services/wsn/wsn-api/pom.xml?rev=1378451&r1=1378450&r2=1378451&view=diff > ============================================================================== > --- cxf/trunk/services/wsn/wsn-api/pom.xml (original) > +++ cxf/trunk/services/wsn/wsn-api/pom.xml Wed Aug 29 06:25:13 2012 > @@ -87,6 +87,7 @@ > javax.xml.bind*;version="[0.0,3)", > javax.jws*;version="[0.0,3)", > javax.xml.ws*;version="[0.0,3)", > + org.apache.cxf.jaxws.spi;version="[2.4,3)", > org.apache.cxf*;version="[2.4,3)", > * > </Import-Package> > > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
