axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5374) Axis2 always assume "text/xml" as SOAP 1.1 content
Date Tue, 24 Jul 2012 19:55:35 GMT


Andreas Veithen commented on AXIS2-5374:

At least part of the logic is in TransportUtils#getContentType. Note that the code is executed
only if doingREST is set to true. Not sure where this flag is set.
> Axis2 always assume "text/xml" as SOAP 1.1 content  
> ----------------------------------------------------
>                 Key: AXIS2-5374
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.5.6, 1.6.2
>            Reporter: Sagara Gunathunga 
>            Assignee: 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message