axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maks (JIRA)" <>
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
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.3
            Reporter: Maks

According to, the Content-Type should have
the following form:

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

The current Axis2 version sends start="", 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:
For additional commands, e-mail:

View raw message