1 Reply Latest reply on Oct 22, 2010 3:35 PM by Nic Essling

    How to get an envelope without header?

    Nic Essling Newbie

      Changed the original title as I found out now that the issue is different than originally thought. Question is rather in my 2nd post of this thread

      ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

       

      All,

       

      via JBoss Dev Studio (using  I created a client for a Web Service based on  a wsdl file as described in

      http://docs.jboss.org/tools/3.1.0.GA/en/ws_ref_guide/html/client.html.

      The generator creates also a client sample. Running this client as a Java application and calling  the remote web service from within this client works perfectly fine. Now  I wanted to call the web service from within a Seam component that is  called by a form within a facelet. I use the same code as in the  stand-alone client's main method, but this time I get this error:

       

      15:33:35,223 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation:

      javax.xml.ws.soap.SOAPFaultException: Could not deserialize Soap message

      at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)

      at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)

      at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:558)

      at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:373)

      at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:231)

      at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:162)

      at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:148)

      at $Proxy224.login(Unknown Source)

      ...

       

      Any idea why the SOAP message cannot be deserialized in this case?

       

       

      Maybe another thing is worth mentioning:

      Running in the app server when I instantiate the web service client by calling

       

      WebService service = new WebService();

       

      I get

       

      10:01:08,850 WARN  [WSDL11Reader] Unprocessed extension element: {http://schemas.xmlsoap.org/wsdl/http/}address
      10:01:08,875 WARN  [WSDL11Reader] Unprocessed extension element: {http://schemas.xmlsoap.org/wsdl/http/}address

       

      which I do not get, if I run this from the sample client as stand-alone Java app.

       

      As I'm stuck at the moment I greatly appreaciate any help!

       

      Thanks

        • 1. Re: SOAPFaultException: Could not deserialize Soap message
          Nic Essling Newbie

          Well, I got one step further by monitoring the traffic with Eclipse's TCP/IP Monitor. What I found out is that in case of the stand-alone Java sample client the SOAP request has just an envelope and a body - which works fine - but in case of running the same code in the app server an empty header element is added into the envelope. This seems to break it as the remote web service runs into an error then.

           

          So, my question is, how can I avoid that a header element is automatically added? Any thoughts?