You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sagara Gunathunga (JIRA)" <ji...@apache.org> on 2012/12/28 12:14:12 UTC
[jira] [Resolved] (AXIS2-5374) Axis2 always assume "text/xml" as
SOAP 1.1 content
[ https://issues.apache.org/jira/browse/AXIS2-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sagara Gunathunga resolved AXIS2-5374.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
Fixed in r1387522.
> 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.5.6, 1.6.2
> Reporter: Sagara Gunathunga
> Assignee: Sagara Gunathunga
> Priority: Critical
> Fix For: 1.7.0
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org