Client Proxy Issue

[shaheenas113483]

In 6.3 instance, the client proxy has:

javax.xml.ws,version=2.1.0 from org.apache.felix.framework (0)

javax.xml.ws.handler,version=2.1.0 from org.apache.felix.framework (0)

while in 6.5 instance for the same pom.xml file the client proxy is showing:

javax.xml.ws,version=2.2.0 from org.apache.servicemix.specs.jaxws-api-2.2 (23)

javax.xml.ws.handler,version=2.2.0 from org.apache.servicemix.specs.jaxws-api-2.2 (23).

and while performing the same functionlity in both the instance, im getting the error in 6.5 as :

FactoryFinder$ConfigurationError: Provider org.apache.cxf.jaxws.spi.ProviderImpl not found

  at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:143) [org.apache.servicemix.specs.jaxws-api-2.2:2.9.0]

What to do?

[Jaideep_Brar]

As per the dependency finder in 6.5, javax.xml.ws depends on the "org.apache.servicemix.specs.jaxws-api-2.2" version 2.9

Can you check if the correct version of the API is installed on the system?

Also, make sure you have compiled the code with the latest version of the uber jar for 6.5

[shaheenas113483]

I have verified the javax.xml.ws and apache serviceMix as well. It looks same as your screenshot. And, the latest version of the uber jar for 6.5 was also used. Still no luck.

[pdeorio]

I'm having the same exact issue - using uber jar 6.5.0. The correct version of the API is installed on my instance as per JaideepBrar​'s screens

[vinaym13734422]

I have the same issue on 6.5.1, did anyone find a solution to this ? Tried with SP-2 also, still the same.

[Bharath_valse]

This seems to be a known issue due to Apache Service Mix. Installing the attached minimum required CXF bundles on my 6.5 helped resolve the issue

Attachment - Adobe Document Cloud

[vinaym13734422]

Thanks Bharath valse​, this works now

[pdeorio]

Thank you Bharath valse​, your package fixed our issue.

[viruh15818023]

We have a similar issue on 6.5.4. installing these package resolved the error but introduced a new bug where the security header is null. Unable to get a security header from the soap object. 

just curious do we need to change the WS client code?  

[sagar_verliani]

@viruh15818023 did you found solution for the null security header, we are stuck on the same issue?

[viruh15818023]

@sgar_verliani, I've resolved this issue by creating a new security header object if it's null. so it worked. 

[sagar_verliani]

Thank you @viruh15818023 , will try creating a new security header object, could you please share reference code snippet for the same.