Hello. I've done more tests, and I've found why the attachment key appears to be bad : it was an error of mine using soapUI attachments. Changing the related content id in the request to match the attachment part of the body, it works as expected. I hope that SOAP frameworks client do it well too... I've also succeeded to use the attachment itself from the Camel message attachment, getting the DataHandler input stream to simply save it (it's just an example) to a file endpoint. Indeed, it seems that the file (file2) component knows how handle an input stream to write a file... A question stays open : do CXF and Camel component support streaming of the attached parts ? I've read ambiguous posts about the "non-ordering" of parts in MTOM exchanges. What is the good way to get big attached files without loading them entirely and stream them to some output target (file, outgoing SOAP call, etc.) ? Thanks again for your help. Regards.
-- View this message in context: http://servicemix.396122.n5.nabble.com/CXF-MTOM-attachments-Camel-access-tp5723342p5723343.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
