Hi. IIRC ODE does not use Axiom internally and converts to DOM (Please correct me if I'm wrong).. Axiom has support for carrying binary data in accordance with XOP/MTOM specs, through OMtext nodes. But I'm not sure how ODE handles the conversion to/from Axiom. There is a very good chance that ODE model will get the binary data in a OMText as a base64 string in the DOM text node, as OMText.getText() will automatically do the conversion in case it contains binary. This is still valid MTOM, but rather little inefficient and lacks the ability to handle very large binary data pieces. If this is not working, then it should be a very trivial fix to the conversion code.
I don't think ODE will support sending MTOM messages, as there is no way to configure the output as MTOM, unless MTOM policy kicks in.. thanks, Thilina On Thu, Jul 9, 2009 at 6:43 PM, Matthieu Riou <[email protected]>wrote: > On Tue, Jul 7, 2009 at 3:00 PM, Marcel Casado <[email protected]> wrote: > > > Hi, > > > > I have a process that calls an external service and the external service > > returns MTOM attachments. Can I copy them and return them to the process > > response? Do I need to enable MTOM in some way on ODE ? Is there any > test > > case ? > > > > No test case but MTOM is provided by Axis2 so it should be fairly > transparent from ODE's standpoint. If I remember correctly, MTOM needs to > be > enabled explicitly though, I'd check the Axis2 doc. > > Matthieu > > > > > > Thanks, > > > > -Marcel > > > -- Thilina Gunarathne - http://thilinag.blogspot.com
