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 "Nigel Furber (JIRA)" <ji...@apache.org> on 2007/08/13 17:19:32 UTC
[jira] Created: (AXIS2-3118) Unable to send Mime multipart
attachment with Axis2 1.3
Unable to send Mime multipart attachment with Axis2 1.3
-------------------------------------------------------
Key: AXIS2-3118
URL: https://issues.apache.org/jira/browse/AXIS2-3118
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.3
Environment: Windows XP SP2, Sun JDK 1.5.08
Reporter: Nigel Furber
I have been using an Axis2 1.2 Axiom client to send mime multipart documents to a Sun JAXRPC - based server. Last week I upgraded to Axis2 1.3RC2 to take advantage of the recent CUSTOM_PROTOCOL_HANDLER/custom SSLProtocolSocketFactory enhancements as I need to be able to make multiple SSL connections using different client certificates. The change allowed that to happen, but prevented the client from working if I try to send attachments. Having compared the messages in some detail, the difference is in the Content-Type of the header.
Release 1.2 gives Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_6437B4F1594AE9FBC11187012706648; type="text/xml"; start="<0....@apache.org>"; charset=UTF-8
Release 1.3RC2 gives Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_93B2FAD54121ADAD431187002026767; type="text/xml"; start="0.urn:uuid:93B2FAD54121ADAD431187002026768@apache.org"; charset=UTF-8
The key difference is the omission of the "<" and ">" at beginning and end of "start=..." I have captured a 1.2-origin successful message using TCPMON and removed the <>, resent it, and it fails. When I then reinstate the <> to the same message and resend it is accepted. Apologies if I have missed a trick in switching them on and off somehow. Regards Nigel Furber
--
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
[jira] Commented: (AXIS2-3118) Unable to send Mime multipart
attachment with Axis2 1.3
Posted by "Nigel Furber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520237 ]
Nigel Furber commented on AXIS2-3118:
-------------------------------------
I think the problem may lie within Axiom;I have now found if you swap the axiom jars from 1.2.5 back to 1.2.4 ( version in Axis2-1.2) the problem goes away. Obviously that re-introduces problems fixed in the 1.2.5 release; however it lets me do some testing! Jars affected are axiom-api-1.2.5.jar, axiom-dom-1.2.5.jar, axiom-impl-1.2.5.jar. Nigel Furber
> Unable to send Mime multipart attachment with Axis2 1.3
> -------------------------------------------------------
>
> Key: AXIS2-3118
> URL: https://issues.apache.org/jira/browse/AXIS2-3118
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Windows XP SP2, Sun JDK 1.5.08
> Reporter: Nigel Furber
>
> I have been using an Axis2 1.2 Axiom client to send mime multipart documents to a Sun JAXRPC - based server. Last week I upgraded to Axis2 1.3RC2 to take advantage of the recent CUSTOM_PROTOCOL_HANDLER/custom SSLProtocolSocketFactory enhancements as I need to be able to make multiple SSL connections using different client certificates. The change allowed that to happen, but prevented the client from working if I try to send attachments. Having compared the messages in some detail, the difference is in the Content-Type of the header.
> Release 1.2 gives Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_6437B4F1594AE9FBC11187012706648; type="text/xml"; start="<0....@apache.org>"; charset=UTF-8
> Release 1.3RC2 gives Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_93B2FAD54121ADAD431187002026767; type="text/xml"; start="0.urn:uuid:93B2FAD54121ADAD431187002026768@apache.org"; charset=UTF-8
> The key difference is the omission of the "<" and ">" at beginning and end of "start=..." I have captured a 1.2-origin successful message using TCPMON and removed the <>, resent it, and it fails. When I then reinstate the <> to the same message and resend it is accepted. Apologies if I have missed a trick in switching them on and off somehow. Regards Nigel Furber
--
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
[jira] Commented: (AXIS2-3118) Unable to send Mime multipart
attachment with Axis2 1.3
Posted by "Nigel Furber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520256 ]
Nigel Furber commented on AXIS2-3118:
-------------------------------------
I think now maybe the problem lies around line 155-180 of org.apache.axiom.om.OMOutputFormat.java.
public String getContentTypeForMTOM(String SOAPContentType) {
StringBuffer sb = new StringBuffer();
sb.append("multipart/related");
sb.append("; ");
sb.append("boundary=");
sb.append(getMimeBoundary());
sb.append("; ");
sb.append("type=\"" + MTOMConstants.MTOM_TYPE + "\"");
sb.append("; ");
sb.append("start=\"").append(getRootContentId()).append("\"");
sb.append("; ");
sb.append("start-info=\"").append(SOAPContentType).append("\"");
return sb.toString();
}
public String getContentTypeForSwA(String SOAPContentType) {
StringBuffer sb = new StringBuffer();
sb.append("multipart/related");
sb.append("; ");
sb.append("boundary=");
sb.append(getMimeBoundary());
sb.append("; ");
sb.append("type=\"").append(SOAPContentType).append("\"");
sb.append("; ");
sb.append("start=\"").append(getRootContentId()).append("\"");
return sb.toString();
}
Certainly the <> s are not being added here. I should have mentioned I have SwA enabled. Nigel Furber
> Unable to send Mime multipart attachment with Axis2 1.3
> -------------------------------------------------------
>
> Key: AXIS2-3118
> URL: https://issues.apache.org/jira/browse/AXIS2-3118
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Windows XP SP2, Sun JDK 1.5.08
> Reporter: Nigel Furber
>
> I have been using an Axis2 1.2 Axiom client to send mime multipart documents to a Sun JAXRPC - based server. Last week I upgraded to Axis2 1.3RC2 to take advantage of the recent CUSTOM_PROTOCOL_HANDLER/custom SSLProtocolSocketFactory enhancements as I need to be able to make multiple SSL connections using different client certificates. The change allowed that to happen, but prevented the client from working if I try to send attachments. Having compared the messages in some detail, the difference is in the Content-Type of the header.
> Release 1.2 gives Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_6437B4F1594AE9FBC11187012706648; type="text/xml"; start="<0....@apache.org>"; charset=UTF-8
> Release 1.3RC2 gives Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_93B2FAD54121ADAD431187002026767; type="text/xml"; start="0.urn:uuid:93B2FAD54121ADAD431187002026768@apache.org"; charset=UTF-8
> The key difference is the omission of the "<" and ">" at beginning and end of "start=..." I have captured a 1.2-origin successful message using TCPMON and removed the <>, resent it, and it fails. When I then reinstate the <> to the same message and resend it is accepted. Apologies if I have missed a trick in switching them on and off somehow. Regards Nigel Furber
--
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