Re: mimeErrorParsing when MTOM is set as the attachment encapsulation type within the service

[paul slade <sl...@gmail.com>]

On 2/4/06, paul slade <sl...@gmail.com> wrote:
>
> I am using the latest Axis 1.x from SVN.
>
> I am have a service with a method called 'download' that returns a
> DataHandler.
>
> I have the following code within this method:
>
> Message rspmsg = AxisEngine.getCurrentMessageContext
> ().getResponseMessage();
>
> rspmsg.getAttachmentsImpl().setSendType(
> org.apache.axis.attachments.Attachments.SEND_TYPE_MTOM);
>
> The client is having issues parsing the Multipart/Related stream returned
> by this method. I am getting a javax.mail.internet.ParseException thrown
> from MultiPartRelatedInputStream:114
>
> javax.mail.internet.ContentType ct =
>
> new javax.mail.internet.ContentType(contentType);
>
> I am able to upload attachements from the client to the server (using
> MTOM). When I compare the Content-Type headers generated by the client (on
> an upload) versus the server (on a download) I see the following:
>
> Good (generated by client on upload):
>
> Content-Type: multipart/related;type="application/xop+xml";
> start="<A14CBC258F65C2E949C8DF2AFE07BF80>"; start-info="text/xml;
> charset=utf-8"; boundary="----=_Part_0_18055655.1138966022050"
>
> Bad (generated by server on download):
>
> Content-Type: multipart/related;type="application/xop+xml";
> start="<066DB20237D367A9B8B855AB14D7B2E7>"; start-info="text/xml;
> boundary="----=_Part_4_19556074.1138967887392";charset=utf-8
>
> Notice the different position of the charset and boundary. Has anyone
> encountered this?
>
> Cheers,
>
> paul
>