Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-5374

Axis2 always assume "text/xml" as SOAP 1.1 content

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.5.6, 1.6.2
    • Fix Version/s: 1.7.0
    • Component/s: kernel
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sagara Sagara Gunathunga
                Reporter:
                sagara Sagara Gunathunga
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: