Sagara Gunathunga created AXIS2-5374:
-----------------------------------------
Summary: Axis2 always assume "text/xml" as SOAP 1.1 content
Key: AXIS2-5374
URL: https://issues.apache.org/jira/browse/AXIS2-5374
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.6.2, 1.5.6
Reporter: Sagara Gunathunga
Priority: Critical
Axis2 REST guide contains following text
"if the content type is text/xml and if the SOAPAction Header is missing, then
the message is treated as a RESTful Message, if not it is treated as a usual
SOAP Message."
In summery
content type - text/xml + SOAPAction present => SOAP 1.1
content type - text/xml + NO SOAPAction present => POX (REST)
In contrast Axis2 never implemented above logic and always consider text/xml as
SOAP 1.1. This issue can be solved by adding a condition to
TransportUtils#getMessageFormatter() so that it will check "SOAPAction" header
in addition to "text/xml" content type.
Before I implement above solution I like see any objection from users and
developers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
