axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maks (JIRA)" <j...@apache.org>
Subject [jira] Created: (AXIS2-3649) Worng Content-Type HTTP header when sending MTOM (incompatible with JBossWS)
Date Fri, 21 Mar 2008 20:43:24 GMT
Worng Content-Type HTTP header when sending MTOM (incompatible with JBossWS)
----------------------------------------------------------------------------

                 Key: AXIS2-3649
                 URL: https://issues.apache.org/jira/browse/AXIS2-3649
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.3
            Reporter: Maks


According to http://ws.apache.org/axis2/1_2/mtom-guide.html, the Content-Type should have
the following form:

Content-Type: multipart/related; boundary=MIMEBoundary4A7AE55984E7438034;
                         type="application/xop+xml"; start="<0.09BC7F4BE2E4D3EF1B@apache.org>";
                         start-info="text/xml; charset=utf-8"

The current Axis2 version sends start="0.09BC7F4BE2E4D3EF1B@apache.org", without angle brackets.
This gets incompatibility with JBossWS, which expects angle brackets.

JBossWS reports error for such Content-Type:
multipart/related stream invalid, no root part was found

The other implementations: JBossWS, JAXWS-RI and .NET do include angle brackets for start
value in Content-Type - that's why I think it is correct behaviour to include them.



-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message