Hi Thilina, Thank you for your reply. Even after changing the case, I am getting the same error.
Thanks & Regards Siva On Thu, Jan 8, 2009 at 10:01 PM, Thilina Gunarathne <[email protected]>wrote: > Hi, > hmmm... weired... I can see the content-id in your messages. But somehow > Axis2 seems to be unable to parse the content-id field. IIRC Axis2 is > suppose to accept content-id irrespective of the case. > > If possible can you try changing the case and see whether it works... > Please log a jira if that was the case... > > thanks, > Thilina > > > On Thu, Jan 8, 2009 at 5:41 AM, SivaKrishna Kumar <[email protected]>wrote: > >> Hello All: >> >> This is Siva from Hyderabad, India. Can you please help me in an issue. >> Here is what I am stuck at. >> >> Zolera SOAP Infrastructure (ZSI) is an open source API written in Python >> for Web Services. ZSI doesn't support MTOM for attachment uploads/downloads >> over web services. I am trying to add this functionality to ZSI. >> >> For this I have modified ZSI to send attachments using MTOM. My >> developement environment is >> >> I am using Apache's Axis2 server for testing attachment upload. As you are >> aware, Axis2 comes with an example for attachments uploading using MTOM. I >> have written a client in Python which will talk to Axis2 server using ZSI. >> When I tried to run the MTOM Sample client that is written in Python with >> the changes made to ZSI for MTOM, I am getting the below error. >> >> "Part content ID cannot be blank for non root MIME parts" >> >> Here is the MTOMized SOAP message and the headers I am sending to the >> Axis2. >> >> ************************************************************************************************************************************************************************************************************************************************************************* >> MIME SOAP Message: >> >> --==ZSI_MIME_BOUNDARY== >> Content-Transfer-Encoding: 7bit >> Content-Type: application/xop+xml; type="text/xml" >> Content-ID: <soaplibEnvelope> >> >> <ns0:Envelope >> xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/";><ns0:Header >> /><ns0:Body><ns1:AttachmentRequest xmlns:ns1=" >> http://ws.apache.org/axis2/mtomsample/";><ns1:fileName>w:\WirelessDiagLog_axis_mtomexample_saved.rar</ns1:fileName><ns1:binaryData><ns2:Include >> href="cid:ZSIAttachment_1" xmlns:ns2=" >> http://www.w3.org/2004/08/xop/include"; >> /></ns1:binaryData></ns1:AttachmentRequest></ns0:Body></ns0:Envelope> >> --==ZSI_MIME_BOUNDARY== >> Content-Type: application/octet-stream >> Content-Transfer-Encoding: 8bit >> Content-ID: <ZSIAttachment_1> >> >> //binary conent of the file >> --==ZSI_MIME_BOUNDARY==-- >> >> >> ************************************************************************************************************************************************************************************************************************************************************************* >> >> Headers: >> >> SOAPAction: '"attachment"' >> Content-Length: 1213 >> Content-Type: 'multipart/related; boundary="==ZSI_MIME_BOUNDARY=="; >> type="application/xop+xml"; start-info="text/xml"; >> start="<soaplibEnvelope>"' >> >> ************************************************************************************************************************************************************************************************************************************************************************* >> >> I am not able to understand where is the problem in the changes I made to >> ZSI for adding MTOM support. >> >> Can you please help me out in this regard ? >> >> Thank you in advance, >> Regards >> Siva >> > > > > -- > Thilina Gunarathne - http://thilinag.blogspot.com >
