[ 
https://issues.apache.org/jira/browse/KARAF-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182310#comment-14182310
 ] 

Freeman Fang commented on KARAF-3332:
-------------------------------------

Hi,

The default org.apache.cxf.jaxws.spi.ProviderImpl as DEFAULT_JAXWSPROVIDER is 
actually from org.apache.geronimo.specs:geronimo-jaxws_2.2_spec which is 
wrapped by org.apache.servicemix.specs.jaxws-api-2.2-2.4.0.jar.

But it's just a default fallback class when can't find any jaxws impl from your 
Karaf container. So if you deploy any other jaxws impl as bundles into Karaf, 
it would be loaded.

Freeman

> Karaf fails to find default Jax Ws provider - searches for CXF
> --------------------------------------------------------------
>
>                 Key: KARAF-3332
>                 URL: https://issues.apache.org/jira/browse/KARAF-3332
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.0.0.M1
>            Reporter: Ioan Eugen Stan
>            Assignee: Freeman Fang
>
> I'm building an application using Jax-Ws:
> -----
> URL url = new 
> URL("http://ec.europa.eu/taxation_customs/vies/services/checkVatService";);
> QName qName = new QName("urn:ec.europa.eu:taxud:vies:services:checkVat", 
> "checkVatService");
> Service service = Service.create(url, qName);
> CheckVatPortType servicePort = service.getPort(CheckVatPortType.class);
> ------
> I get the following error
> ----
> Caused by: javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider 
> org.apache.cxf.jaxws.spi.ProviderImpl not found
>       at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:143)
> ....  
> ----
> It seams that Karaf has a jar file 
> lib/endorsed/org.apache.servicemix.specs.jaxws-api-2.2-2.4.0.jar that 
> searches for CXF as a default implementation, and does not find the standard 
> provider (not based on CXF). 
> Runnning the same code outside OSGi works, not requiring CXF. 
> I do not like pulling all CXF dependencies into my projects. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to