You have configured your service to use SOAP with Attachments, but the client only supports MTOM.
Andreas On Tue, Jul 21, 2009 at 18:38, Sumit Shah<[email protected]> wrote: > Thanks Colin. Basically the problem I am running into is that Axis2 is > generating the message as below: > > > > HTTP/1.1 200 OK > Cache-Control: no-cache="Set-Cookie" > Connection: close > Date: Wed, 15 Jul 2009 14:51:22 GMT > Content-Type: multipart/related; > boundary=MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559; > type="application/soap+xml"; > start="<0.urn:uuid:[email protected]>"; > action="urn:reviewResponse" > Set-Cookie: > JSESSIONID=2hdGKdsKlDvVZyLDfY69d7R3GxTh1gLQxp1124l1nPLsn5j1ynRq!1516756995; > path=/ > X-Powered-By: Servlet/2.5 JSP/2.1 > > --MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559 > Content-Type: application/soap+xml; charset=UTF-8 > Content-Transfer-Encoding: 8bit > Content-ID: <0.urn:uuid:[email protected]> > > <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><SOME > RESPONSE ></soapenv:Body></soapenv:Envelope> > --MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559-- > > Apparently the consuming app thinks that the message type > “application/soap+xml” is invalid for this message and instead needs it to > be “application/xop+xml”. I am guessing it is because of the > multipart/related. I may be wrong though. I am trying to figure out if there > is way (some settings in the axis2.xml, etc.) to have the consuming app not > think that the message should be of application/xop+xml? > > > > Thanks > > Sumit > > > > > > > > ________________________________ > > From: [email protected] [mailto:[email protected]] > Sent: Tuesday, July 21, 2009 10:12 AM > To: [email protected] > Cc: [email protected]; [email protected] > Subject: Re: What generates the MIME boundary in the SOAP/HTTP message? > > > > The Content-Type field for multipart entities requires one parameter, > "boundary". > > The rules for MIME boundary markers can be found in the MIME specifications, > in section 5.1.1 of RFC 2046 > > The boundary delimiter consists of a line starting with a hyphen pair, > followed by a boundary string. This sequence must not occur within the MIME > message at any point other than as a boundary. A MIME end-delimiter is a > hyphen pair, followed by the MIME boundary string, followed by a further > hyphen pair. All delimiter lines must end in the ASCII sequence <CR><LF>. An > example of a delimited message is: > > --MIME_boundary > message data > --MIME_boundary > message data > --MIME_boundary-- > > where MIME_boundary is the boundary delimiter string, and message data > represents message data. > > Regards, > > Colin > > > > "Sumit Shah" <[email protected]> > > 07/20/2009 02:32 PM > > Please respond to > [email protected] > > To > > <[email protected]>, <[email protected]> > > cc > > > > Subject > > What generates the MIME boundary in the SOAP/HTTP message? > > > > > > > > > All, > > I am trying to find out what triggers the generation of the MIME boundary in > the SOAP/HTTP. Apparently I’m having issues with the MIME boundary being > present in the message? Apparently an integrating application thinks that > the content-type needs to be application/xop+xml. > > I would appreciate if you have any suggestions/ideas. > > Thanks > Sumit > > > Sample Message > > HTTP/1.1 200 OK > Cache-Control: no-cache="Set-Cookie" > Connection: close > Date: Wed, 15 Jul 2009 14:51:22 GMT > Content-Type: multipart/related; > boundary=MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559; > type="application/soap+xml"; > start="<0.urn:uuid:[email protected]>"; > action="urn:reviewResponse" > Set-Cookie: > JSESSIONID=2hdGKdsKlDvVZyLDfY69d7R3GxTh1gLQxp1124l1nPLsn5j1ynRq!1516756995; > path=/ > X-Powered-By: Servlet/2.5 JSP/2.1 > > --MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559 > Content-Type: application/soap+xml; charset=UTF-8 > Content-Transfer-Encoding: 8bit > Content-ID: <0.urn:uuid:[email protected]> > > <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><SOME > RESPONSE ></soapenv:Body></soapenv:Envelope> > --MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559-- > > ________________________________ > > This transmittal and any attachments may contain confidential, privileged or > sensitive information and is solely for the use of the intended recipient. > If you are not the intended recipient, you are hereby notified that you have > received this transmittal and any attachments in error and any review, > dissemination, distribution or copying thereof is strictly prohibited. If > you have received this transmittal and any attachments in error please > notify the sender and immediately destroy the message and all its > attachments. Any opinions herein expressed may be those of the author and > not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), > Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group > ("Mizuho"). Mizuho accepts no responsibility for the accuracy or > completeness of any information herein contained. > E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which > is a registered U.S. broker-dealer and the entity through which Mizuho > generally conducts its investment banking, capital markets, and securities > business in the United States) is electronically archived and recorded and > is subject to review and monitoring by and/or disclosure to persons other > than the recipient, including (but not limited to) Mizuho Securities USA > Inc. supervisory personnel. Such communications may be produced to > regulatory authorities or others with legal rights to the information. > If you have any questions, or if you no longer wish to receive e-mail in > accordance with Japanese Act on Regulation of the Transmission of Specified > Electronic Mail, please contact the sender of this e-mail. > お問い合わせまたは特定電子メール法に 基づく送信停止のご要望等は、本電子メールの送信者にその旨ご連絡ください。
