ClassCastException while sending headers to docManClient

Hi!

I'm trying to invoke a document manager service method from my axis2-based web-service and while passing auth token to headers this line:

((WSBindingProvider) docManClient).setOutboundHeaders(Headers.create(otAuthElement));

returns a ClassCastException:

com.sun.proxy.$Proxy283 cannot be cast to com.sun.xml.internal.ws.developer.WSBindingProvider

My code is pretty standart, I got it from CWS example and it works perfectly from simple java application but from my webservice it does not. Is there something I should know when invoking webservice from another webservice?

Please help.

Find more posts tagged with

Comments

Maxim_Chernyaev

So apparently when used from web-service method getBasicHttpBindingDocumentManagement() returns some kind of proxy totally different object which can not be casted. I've found out that there's a getBasicHttpBindingDocumentManagement(WebServiceFeature...) option of invoking that method, is there a example or tutorial of how to use it from web service?

Maxim_Chernyaev

Please help, cause I still have this ClassCastException problem.

Has anybody ever tried using cws from another web service?

Maxim_Chernyaev

For those who facing the same problem:

My solution was to use javax.xml.ws.BindingProvider class instead of com.sun.xml.internal.ws.developer.WSBindingProvider. This way casting went well.

Although I had to use different way to form a SOAPHeader and add it to envelope, but there's a lot of info on how to do that on the net.

svinchon

Hello!

Would you mind posting the code you had to use to add the SOAP header using javax.xml.ws.BindingProvider instead of com.sun.xml.internal.ws.developer.WSBindingProvider?

I am facing the exact same issue as you.

Regards,

Sebastien

Sean_Lapointe

I am also facing the exact same issue. Can Maxim, or anyone else, help with this?

svinchon

I got it to work.

I am going to try to attach the adjusted "GettingStarted.java" code.

svinchon

Here is the attachement.

Sean_Lapointe

I fixed my issue.

Like Maxim mentioned, I had to use a different binding class and make the soap header differently.

I found an example of a SOAP header handler class here(near the bottom of the page) https://stackoverflow.com/questions/2322953/jax-ws-adding-soap-headers

I did the casting like this:

Binding binding = ((BindingProvider) serviceClient).getBinding();

List handlers = binding.getHandlerChain();

handlers.add(new SOAPHeaderHandler(otAuth.getAuthenticationToken()));

binding.setHandlerChain(handlers);

Once I did that, I still had some trouble with the headers (first I was creating two header elements, then none) so I used a class I found to output the SOAP envelope to the console after adding the logging handler to the chain. Once I could see the entire envelope, I solved the rest of my issues. https://stackoverflow.com/questions/1945618/tracing-xml-request-responses-with-jax-ws