You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Soyer, Muhammed A." <MS...@MICROS.COM> on 2008/10/02 16:06:11 UTC

Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI

Hi,
  I am getting an error[1] when I do a call to a .Net service by using and axis2 1.4.1 client.  I did some research and I found that axis throws this error when it can't be sure about the soap version of the message.[2]
I want to be sure that I am understanding correctly. According to the link below my message must have the Content type of http header as "application/soap+xml" not as text/xml.
Is this a correct statement?
Is there any quick workaround?

Thanks


1-org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI
2-http://wso2.org/library/559


----

HTTP/1.1 200 OK
Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428
Date: Thu, 02 Oct 2008 13:31:47 GMT
Content-Type: text/xml; charset=utf-8
Content-Length: 1256

<env:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header>
      <wsa:MessageID>uuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05</wsa:MessageID>
      <wsa:RelatesTo>urn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d</wsa:RelatesTo>
      <wsa:To>soap.tcp://abcd:3456/</wsa:To>
      <wsa:Action>http://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse</wsa:Action>
      <wsu:Timestamp wsu:Id="Timestamp-ea6490c2-d8a6-49ce-a09b-d02cd8f6b03f">
         <wsu:Created>2008-10-02T13:31:47Z</wsu:Created>
         <wsu:Expires>2008-10-02T13:41:47Z</wsu:Expires>
      </wsu:Timestamp>
      <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
   </env:Header>
   <env:Body>
      <BeginCreateResponse xmlns:tns="http://www.zzz.com/BPEL/OpenActivity/CentralReservation/" xmlns="http://www.zzz.com/BPEL/OpenActivity/CentralReservation/">
         <tns:ProcessID>f12fce7e-155e-4c02-871c-16254637fac7</tns:ProcessID>
      </BeginCreateResponse>
   </env:Body>
</env:Envelope>

RE: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI

Posted by "Soyer, Muhammed A." <MS...@MICROS.COM>.
Thanks for your reply, I already tried what you suggested and that is working.

-ms

From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Thursday, October 02, 2008 11:00 AM
To: axis-user@ws.apache.org
Subject: Re: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI


On Thu, Oct 2, 2008 at 7:36 PM, Soyer, Muhammed A. <MS...@micros.com>> wrote:

Hi,

  I am getting an error[1] when I do a call to a .Net service by using and axis2 1.4.1 client.  I did some research and I found that axis throws this error when it can't be sure about the soap version of the message.[2]

I want to be sure that I am understanding correctly. According to the link below my message must have the Content type of http header as "application/soap+xml" not as text/xml.

Is this a correct statement?
Yes. Your soap envelop is SOAP 1.2 ( cause its namespace is http://www.w3.org/2003/05/soap-envelope) hence its content-type should be application/soap+xml. The content-type of SOAP 1.1 is text/xml. So there is a problem in your response.

I presume that Axis2 sent a SOAP 1.2 request (cause this is the default in Axis2). As a workaround try sending a SOAP 1.1 request. You could do this by setting the following on the options object,

options.setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);

But the Server is definitely in fault here and not Axis2. You may wanna raise an issue against it.

Thanks,
Keith.

Is there any quick workaround?



Thanks





1-org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI
2-http://wso2.org/library/559





----



HTTP/1.1 200 OK

Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428

Date: Thu, 02 Oct 2008 13:31:47 GMT

Content-Type: text/xml; charset=utf-8

Content-Length: 1256



<env:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:env="http://www.w3.org/2003/05/soap-envelope">

   <env:Header>

      <wsa:MessageID>uuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05</wsa:MessageID>

      <wsa:RelatesTo>urn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d</wsa:RelatesTo>

      <wsa:To>soap.tcp://abcd:3456/</wsa:To>

      <wsa:Action>http://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse</wsa:Action>

      <wsu:Timestamp wsu:Id="Timestamp-ea6490c2-d8a6-49ce-a09b-d02cd8f6b03f">

         <wsu:Created>2008-10-02T13:31:47Z</wsu:Created>

         <wsu:Expires>2008-10-02T13:41:47Z</wsu:Expires>

      </wsu:Timestamp>

      <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>

   </env:Header>

   <env:Body>

      <BeginCreateResponse xmlns:tns="http://www.zzz.com/BPEL/OpenActivity/CentralReservation/" xmlns="http://www.zzz.com/BPEL/OpenActivity/CentralReservation/">

         <tns:ProcessID>f12fce7e-155e-4c02-871c-16254637fac7</tns:ProcessID>

      </BeginCreateResponse>

   </env:Body>

</env:Envelope>





--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI

Posted by keith chapman <ke...@gmail.com>.
On Thu, Oct 2, 2008 at 7:36 PM, Soyer, Muhammed A. <MS...@micros.com>wrote:

>  Hi,
>
>   I am getting an error[1] when I do a call to a .Net service by using and
> axis2 1.4.1 client.  I did some research and I found that axis throws this
> error when it can't be sure about the soap version of the message.[2]
>
> I want to be sure that I am understanding correctly. According to the link
> below my message must have the Content type of http header as
> "application/soap+xml" not as text/xml.
>
> Is this a correct statement?
>
Yes. Your soap envelop is SOAP 1.2 ( cause its namespace is *
http://www.w3.org/2003/05/soap-envelope) *hence its content-type should be
application/soap+xml. The content-type of SOAP 1.1 is text/xml. So there is
a problem in your response.

I presume that Axis2 sent a SOAP 1.2 request (cause this is the default in
Axis2). As a workaround try sending a SOAP 1.1 request. You could do this by
setting the following on the options object,

options.setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);

But the Server is definitely in fault here and not Axis2. You may wanna
raise an issue against it.

Thanks,
Keith.

> Is there any quick workaround?
>
>
>
> Thanks
>
>
>
>
>
> 1-org.apache.axis2.AxisFault: Transport level information does not match
> with SOAP Message namespace URI
> 2-http://wso2.org/library/559
>
>
>
>
>
> ----
>
>
>
> HTTP/1.1 200 OK
>
> Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428
>
> Date: Thu, 02 Oct 2008 13:31:47 GMT
>
> *Content-Type: text/xml; charset=utf-8*
>
> Content-Length: 1256
>
>
>
> <env:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
> xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance" *xmlns:env="
> http://www.w3.org/2003/05/soap-envelope*">
>
>    <env:Header>
>
>
> <wsa:MessageID>uuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05</wsa:MessageID>
>
>
> <wsa:RelatesTo>urn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d</wsa:RelatesTo>
>
>       <wsa:To>soap.tcp://abcd:3456/</wsa:To>
>
>       <wsa:Action>
> http://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse
> </wsa:Action>
>
>       <wsu:Timestamp
> wsu:Id="Timestamp-ea6490c2-d8a6-49ce-a09b-d02cd8f6b03f">
>
>          <wsu:Created>2008-10-02T13:31:47Z</wsu:Created>
>
>          <wsu:Expires>2008-10-02T13:41:47Z</wsu:Expires>
>
>       </wsu:Timestamp>
>
>       <wsse:Security xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> "/>
>
>    </env:Header>
>
>    <env:Body>
>
>       <BeginCreateResponse xmlns:tns="
> http://www.zzz.com/BPEL/OpenActivity/CentralReservation/" xmlns="
> http://www.zzz.com/BPEL/OpenActivity/CentralReservation/">
>
>
> <tns:ProcessID>f12fce7e-155e-4c02-871c-16254637fac7</tns:ProcessID>
>
>       </BeginCreateResponse>
>
>    </env:Body>
>
> </env:Envelope>
>
>
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org