Hi naveen, Currently axis2/c codegen doesn't support MTOM. You need to write the code manually to handle mtom attachments. Can you raise a JIRA on this, so it will be easy to track this issue.
Thanks Dimuthu On Wed, Jun 4, 2008 at 3:38 PM, naveen bhat <[EMAIL PROTECTED]> wrote: > Hello group, > > I have a service which receives an MTOM attachment, and the service sends > back the same. > I generated the service skeleton code with adb from the wsdl . > The wsdl describes the data exchanged to be of type xmime:base64binary. > I am able to receive the MTOM attachment at the client and save it to a > file. > In the business logic of the service, i wrote the code to create the > datahandler from the file received. > But i found that the code that is serializing the xop node is converting it > to a string using axiom_node_to_string API. > Because of which i am unable to see the attachment at the client end. > > > *For Instance:* > > Sample server response to client as observed in tcpmon > > > ---MIME boundary > <soapenvelope> > <soapbody> > <BinaryData><xop node serialized as string></BinaryData> > </soapbody> > </soapenvelope> > ----MIME boundary > > ----MIME boundary > No attachment(empty) > ----MIME boundary > > > *Serializer logic:* > > It is enclosing the xop node in between the tags <BinaryData> and > </BinaryData>. > Its converting xop node to string using axiom_node_to_string(xop_node,env)l > > > > How to generate code with proper serializers to send MTOM from the service > with adb??? > Kindly let me know if you need more details. > > Thanks in advance, > Naveen Bhat > > >
