2 Replies Latest reply on Apr 2, 2008 7:45 AM by Norbert Schollum

    Problems with multipart/related responses

    Norbert Schollum Newbie

      Hi everyone,

      we have created a JBossWS Client with version 2.0.1 consuming a Axis2 webservice, that is sending its responses in multipart/related format.

      Everything works fine when testing with SoapUi. but when calling a method with the JBoss client, we get this error message:

      Caused by: java.lang.IllegalArgumentException: multipart/related stream invalid, no root part was found
       at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:164)
       at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:228)
       at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:84)
       at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175)


      I have already tried with the libraries from 2.0.3. But this causes the same problems.

      This is the response received from Axis2 Server:

      HTTP/1.1 200 OK
      Date: Tue, 04 Mar 2008 09:41:08 GMT
      Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217; type="application/xop+xml"; start="0.urn:uuid:98BB2CA94931E2B9C21204623668218@apache.org"; start-info="text/xml"
      Server: Apache-Coyote/1.1
      Transfer-Encoding: chunked
      
      --MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217
      Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
      Content-Transfer-Encoding: binary
      Content-ID: <0.urn:uuid:98BB2CA94931E2B9C21204623668218@apache.org>
      
      <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:loadEloFileUrlResponse xmlns:ns="http://eloservice.giag.com"><ns:return>http://some_url_notshown</ns:return></ns:loadEloFileUrlResponse></soapenv:Body></soapenv:Envelope>
      --MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217--


      Did somebody have similar problems?
      If this is a known issue please let me know.
      Thanks for your help!

      Regards,
      Norbert