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.urn:uuid:[EMAIL PROTECTED]>"; charset=UTF-8
Release 1.3RC2 gives Content-Type: multipart/related; 
boundary=MIMEBoundaryurn_uuid_93B2FAD54121ADAD431187002026767; type="text/xml"; 
start="0.urn:uuid:[EMAIL PROTECTED]"; 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to