[
https://issues.apache.org/jira/browse/AXIS2C-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1181.
-------------------------------------
Fix Version/s: 2.0.0
Resolution: Implemented
1. The original issue was for the old Java-based WSDL2C code generator
2. There is now a native C code generator
3. MTOM support for the native generator is tracked by AXIS2C-1679
4. The analysis and test infrastructure are already in place under the newer
issue
> Unable to support MTOM for code generation with adb
> ---------------------------------------------------
>
> Key: AXIS2C-1181
> URL: https://issues.apache.org/jira/browse/AXIS2C-1181
> Project: Axis2-C
> Issue Type: New Feature
> Components: code generation
> Affects Versions: 1.4.0
> Environment: CentOS 4.4
> Reporter: naveen bhat
> Priority: Major
> Fix For: 2.0.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]