axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "keith chapman" <keithgchap...@gmail.com>
Subject Re: Error : "Transport level information does not match with SOAP Message namespace URI"
Date Wed, 17 Sep 2008 03:51:08 GMT
The problem is not in the SOAPActioion header. The request your client is
sending is incorrect. Your SOAP message is SOAP 1.2 (
http://www.w3.org/2003/05/soap-envelope) as you rightly point out, but its
content-type is test/xml. This is incorrect. The Content-Type for SOAP 1.2
should be application/soap+xml. test/xml is used for SOAP 1.1. This is the
reason for Axis2 to throw the error. Axis2 build messages based on there
content-type. You client is obviously in fault here and you might wanna fix
that.

Thanks,
Keith.

On Wed, Sep 17, 2008 at 2:56 AM, Brian Neate <bneate@alarmpoint.com> wrote:

>  Hello,
>
>
>
> I'm trying to write a axis2 web service to consume web service requests
> sent from a third party application.  The problem I am having is that when
> the third party application sends web service requests to my axis2 web
> service it gets a "Transport level information does not match with SOAP
> Message namespace URI" fault back.  I believe the problem is that the
> request is being made using SOAP 1.2 (
> http://www.w3.org/2003/05/soap-envelope) but there is also a SOAPAction:
> "" header being added to the http request.  Is there any way to tell axis2
> to ignore the extra http header and continue to process the request using
> SOAP 1.2?
>
>
>
> I need to complete the project I am working on very quickly and any help
> would be greatly appreciated.
>
>
>
> Sample request:
>
> POST /api/services/NNMWSEvent HTTP/1.1
>
> SOAPAction: ""
>
> Content-Type: text/xml; charset=UTF-8
>
> JBoss-Remoting-Version: 22
>
> User-Agent: JBossRemoting - 2.2.2.SP7 (Bluto)
>
> Host: 127.0.0.1:8881
>
> Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
>
> Connection: keep-alive
>
>
>
> <env:Envelope xmlns:env='http://www.w3.org/2003/05/soap-envelope'
> xmlns:wsa='http://www.w3.org/2005/08/addressing' xmlns:wse='
> http://schemas.xmlsoap.org/ws/2004/08/eventing'>
>
>    <env:Header>
>
>       <wsa:Action>
> http://notification.sdk.nms.ov.hp.com/nms-sdk-notify/IncidentNotificationSource/Notification
> </wsa:Action>
>
>       <wsa:To>http://neate.bounceme.net:8881/api/services/NNMWSEvent
> </wsa:To>
>
>    </env:Header>
>
>    <env:Body>
>
>       <sys:onNotification xmlns:sys='
> http://notification.sdk.nms.ov.hp.com/nms-sdk-notify'>
>
>          <arg0>
>
>             <id>64424516155</id>
>
>             <uuid>fd6b08c9-9c78-4214-8777-ab30da17e5f07</uuid>
>
>             <name>AddressNotResponding7</name>
>
>             <sourceUuid>4a9596d2-2a70-43a9-97b5-b255980b5db5d</sourceUuid>
>
>             <sourceName>192.168.168.96d</sourceName>
>
>
> <sourceNodeUuid>87c1b801-d12b-4c02-a6ce-2b4b1d91039c11</sourceNodeUuid>
>
>             <sourceNodeName>192.168.168.9611</sourceNodeName>
>
>
> <lifecycleState>com.hp.nms.incident.lifecycle.Registered11</lifecycleState>
>
>             <severity>CRITICALb</severity>
>
>             <priority>com.hp.nms.incident.priority.Noneb</priority>
>
>             <category>com.hp.nms.incident.category.Faultb</category>
>
>             <family>com.hp.nms.incident.family.Address9</family>
>
>             <nature>ROOTCAUSE9</nature>
>
>             <origin>MANAGEMENTSOFTWARE9</origin>
>
>             <duplicateCount>011</duplicateCount>
>
>             <priority>com.hp.nms.incident.priority.Noneb</priority>
>
>             <rcaActive>truec</rcaActive>
>
>             <formattedMessage>Address Not Responding13</formattedMessage>
>
>
> <originOccurrenceTime>2008-09-16T14:04:15.278-07:0017</originOccurrenceTime>
>
>
> <firstOccurrenceTime>2008-09-16T14:04:15.278-07:0016</firstOccurrenceTime>
>
>
> <lastOccurrenceTime>2008-09-16T14:04:15.278-07:0015</lastOccurrenceTime>
>
>             <created>2008-09-16T14:04:16.200-07:00</created>
>
>             <updateTime/>
>
>             <previousLifecycleState/>
>
>             <previousRcaActive/>
>
>             <cias>
>
>                <name>com.hp.ov.nms.apa.symptom7</name>
>
>                <type>STRING7</type>
>
>                <value>ICMPNoResponse8</value>
>
>             </cias>
>
>          </arg0>
>
>       </sys:onNotification>
>
>    </env:Body>
>
> </env:Envelope>
>
>
>
> Axis2 Response:
>
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
>    <soapenv:Header>
>
>       <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
>
>    </soapenv:Header>
>
>    <soapenv:Body>
>
>       <soapenv:Fault>
>
>          <soapenv:Code>
>
>             <soapenv:Value>soapenv:Sender</soapenv:Value>
>
>             <soapenv:Subcode>
>
>                <soapenv:Value>wsa:InvalidAddressingHeader</soapenv:Value>
>
>                <soapenv:Subcode>
>
>                   <soapenv:Value>wsa:ActionMismatch</soapenv:Value>
>
>                </soapenv:Subcode>
>
>             </soapenv:Subcode>
>
>          </soapenv:Code>
>
>          <soapenv:Reason>
>
>             <soapenv:Text xml:lang="en-US">A header representing a Message
> Addressing Property is not valid and the message cannot be
> processed</soapenv:Text>
>
>          </soapenv:Reason>
>
>          <soapenv:Detail>
>
>             <wsa:ProblemHeaderQName>wsa:Action</wsa:ProblemHeaderQName>
>
>          </soapenv:Detail>
>
>       </soapenv:Fault>
>
>    </soapenv:Body>
>
> </soapenv:Envelope>
>
>
>
>
>
> Thanks,
>
> Brian
>
>
>



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

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

Mime
View raw message