[ 
https://issues.apache.org/jira/browse/AXIS2C-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609296#action_12609296
 ] 

Damitha Kumarage commented on AXIS2C-1213:
------------------------------------------

According to soap 1.1 specication

"The header field value of empty string ("") means that the intent of the SOAP 
message is
provided by the HTTP Request-URI. No value means that there is no indication of 
the intent
of the message."

Also according to the same spec

"An HTTP client MUST use the SOAPAction header field when issuing a SOAP HTTP 
Request"

In soap 1.2 media type application/soap+xml optionally defines action parameter.

According to the WSDL version 2.0 Soap 1.1 binding extension

"A SOAP Binding is identified as a SOAP 1.1 binding by assigning the value 
"1.1" to the {soap version}
property of the Binding component."

According to same extension

"SOAP Action. If the Binding Operation component does NOT have a {soap action} 
property defined, then
the quoted empty string value ("") value is used for the SOAP 1.1 SOAPAction 
HTTP Header Field (see [SOAP11])."

Note that for soap 1.2 action is optional. So for wsdl2.0 there could be {soap 
action} not defined.

Read more about this extension
http://www.w3.org/TR/wsdl20-soap11-binding/#soap11-binding


Also accroding to WSDL 1.1 soap 1.2 binding

In binding element

"<wsdl:binding ... >
   <wsoap12:binding transport="xs:anyURI"
                    style="rpc|document" ? ... />"
...
</wsdl:binding>

In operation element
"<wsoap12:operation soapAction="xs:anyURI" ?
                   soapActionRequired="xs:boolean" ?
                   style="rpc|document" ? ... /> ?"

where you need to define 
xmlns:wsoap12="http://schemas.xmlsoap.org/wsdl/soap12/"; in wsdl:definitions
 section.

Since SOAPAction is mandatory when soap 1.1 is used wsdl should have an empty 
SOAPAction string 

> server returns HTTP/1.1 500 Internal Server Error for In-Only message
> ---------------------------------------------------------------------
>
>                 Key: AXIS2C-1213
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1213
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>         Environment: linux fc6
>            Reporter: Frederic Heem
>            Priority: Blocker
>
> After upgrading from svn, In-Only messages stop working correctly: 
> * the server returns HTTP/1.1 500 Internal Server Error
> * the client returns successfully even though the server returns an error:
> Here the conversation between and server:
> POST /axis2/services/zigbee HTTP/1.1
> User-Agent: Axis2C/1.4.0
> SOAPAction: ""
> Content-Length: 507
> Content-Type: text/xml;charset=UTF-8
> Host: localhost:9090
> <soapenv:Envelope 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header 
> xmlns:wsa="http://www.w3.org/2005/08/addressing";><wsa:To>http://localhost:9090/axis2/services/zigbee</wsa:To><wsa:Action>PermitJoining</wsa:Action><wsa:MessageID>5b6a6c86-46b8-1dd1-3722-0014c2e176e7</wsa:MessageID></soapenv:Header><soapenv:Body><n:PermitJoiningParam
>  
> xmlns:n="http://www.telsey.com/DPWS/2008/03/Zigbee";><n:permitDuration>50</n:permitDuration></n:PermitJoiningParam></soapenv:Body></soapenv:Envelope>
> HTTP/1.1 500 Internal Server Error
> Date: Mon Jun 30 16:22:31 2008 GMT
> Server: Axis2C/1.4.0 (Simple Axis2 HTTP Server)
> Content-Type: text/xml;charset=UTF-8
> Content-Length: 370
> <soapenv:Envelope 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header></soapenv:Header><soapenv:Body><soapenv:Fault><faultcode>soapenv:Sender</faultcode><faultstring>NULL
>  parameter was passed when a non NULL parameter was 
> expected</faultstring><detail><TestServiceError></TestServiceError></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to