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.
