Hi, Regarding requirement: One of the project here is using an external web service. When they tested with Sun SAAJ implementation everything worked fine and the body part header looks like: Content-Type: text/xml; charset=utf-8
Content-Id: <[EMAIL PROTECTED]> Since Sun SAAJ is not yet supported here, I am trying to make it work with AXIS2's OperationClient API and the service returns an error. The body part header looks like: content-type: text/xml; charset=UTF-8 content-transfer-encoding: 8bit content-id: <0.urn:uuid:[EMAIL PROTECTED]> So, I was wondering if I could make content-transfer-encoding "binary" or remove it altogether from header. Out of curiosity: Does AXIS2 SwA work with SAAJ ? Thanx -yogen -----Original Message----- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Thursday, February 08, 2007 7:48 AM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Re: MTOM and SWA related problem Currently there is no way to set it. "8-bit" is the encoding we use for the body part of all the SwA messages.. Can you please elaborate your requirement... Thanks, Thilina On 2/7/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> wrote: > Hi, > Thanx, I reached the same conclusion. > Setting "content-transfer-encoding: binary" in Options changes > transfer encoding for multipart/related and not for the part in which > SOAP Body goes. > > Any idea how to make it work? What class of Commons Http Client adds > the SOAP Body part to the message on the wire ? > > Appreciate your feedback. > Thanx > -yogen > > > -----Original Message----- > From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 07, 2007 8:34 AM > To: [email protected] > Cc: [EMAIL PROTECTED] > Subject: Re: MTOM and SWA related problem > > It's not possible to change the encoding of the first part.. > You can change the content-type of the attachment part by creating > your DataHandler using org.apache.axiom.attachments.ConfigurableDataHandler. > ConfigurableDataHandler is behaves same as the DataHandler and it has > a setContentType method.. > > ~Thilina > > On 2/7/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> > wrote: > > Thank you Dims. > > One more question, when I used OperationClient API, the content-type > > and content-transfer-encoding for first part look like this: > > content-type: text/xml; charset=UTF-8 > > content-transfer-encoding: 8bit > > > > And for attachment part look like this: > > content-type: application/octet-stream > > content-transfer-encoding: binary > > > > Is it possible to make "content-transfer-encoding: binary" for the > > first part and "Content-Type: text/xml" for the attachment part ? > > > > Thanx, appreciate it. > > -yogen > > > > > > > > -----Original Message----- > > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 06, 2007 4:22 PM > > To: [email protected] > > Subject: Re: MTOM and SWA related problem > > > > Yogen, > > > > Those are from Commons HTTP Client basically means that the client > > is using http chunking. > > > > thanks, > > dims > > > > On 2/6/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > > > > Hi, > > > Anyone who has used attachments with AXIS2 ? > > > -yogen > > > > > > > > > ________________________________ > > > From: Yadav, Yogendra (IT) > > > Sent: Tuesday, February 06, 2007 3:26 PM > > > To: [email protected] > > > Subject: FW: MTOM and SWA related problem > > > > > > > > > > > > > > > Sorry if this email is repeated multiple times. I had corporate > > > security issues sending attachments. > > > > > > Hi, > > > This problem is related to using MTOM and SAAJ APIs in AXIS2. I am > > > sending attachment to a service which is implemented using Sun's > > > SAAJ implementation. When I use Sun's SAAJ as client to access > > > this service > > > > > everything works well. But when use AXIS2's MTOM or SAAJ > > > implementation, the service returns invalid response. I have > > > noticed > > > > differences in the request message being sent in eiather case in > > > TCPMon and noticed unusual characters in the request generated by > > AXIS2. > > > > > > Can someone explain if these unusual characters are the cause of > > > failure or its something else. > > > > > > Note: If you notice AXIS2's implementations insert unusual > > > characters in the > > > request: > > > 1a97 <----------- > > > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911 > > > 3a <----------- > > > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911-- > > > 0 <----------- > > > > > > 1ba2 <----------- > > > --MIMEBoundaryurn_uuid_6F2725CFB5F14717A21170792657850 > > > 3a <----------- > > > --MIMEBoundaryurn_uuid_6F2725CFB5F14717A21170792657850-- > > > 0 <----------- > > > > > > > > > I have attached below the relevant information from TCPMon . Any > > > help > > > > > is appreciated. > > > > > > thanx > > > -yogen > > > > > > axis2's SAAJ: > > > -------------------- > > > 1a97 > > > > > > --MIMEBoundaryurn_uuid_1E6396FC3B5AC6B6D31170792603911 > > > > > > content-type: application/xop+xml; charset=UTF-8; type="text/xml"; > > > > > > content-transfer-encoding: binary > > > > > > content-id: > > > <0.urn:uuid:[EMAIL PROTECTED]> > > > > > > sun's SAAJ > > > ------------------ > > > ------=_Part_0_20918341.1170792531816 > > > > > > Content-Type: text/xml; charset=utf-8 > > > > > > Content-Id: <[EMAIL PROTECTED]> > > > > > > ________________________________ > > > > > > > > > NOTICE: If received in error, please destroy and notify sender. > > > Sender > > > > > does not intend to waive confidentiality or privilege. Use of this > > > email is prohibited when received in error. > > > > > > ________________________________ > > > > > > > > > NOTICE: If received in error, please destroy and notify sender. > > > Sender > > > > > does not intend to waive confidentiality or privilege. Use of this > > > email is prohibited when received in error. > > > > > > > > > -- > > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services > > Developers > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -------------------------------------------------------- > > > > NOTICE: If received in error, please destroy and notify sender. > > Sender > does not intend to waive confidentiality or privilege. Use of this > email is prohibited when received in error. > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Thilina Gunarathne > WSO2, Inc.; http://www.wso2.com/ > Home page: http://webservices.apache.org/~thilina/ > Blog: http://thilinag.blogspot.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -------------------------------------------------------- > > NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
