I believe camel-cxf can do this task.
My messages are not WSDL compliant but wrapped inside SOAP. So don't need the CXF stack/capabilities. CXF mandates wsdl usage(?).
tried bit camel-soap which is cxf minus wsdl but it relies on JAXB. I need my XML's as Input/DOM..or atleast a as String sources.
I could write my own marshaller but don't want to get into that as I am supposed to analyze how well this product (Fuse/ESB) fits out of box for our application POC.
So you just want to handle the attachements with SOAP message.
You can implement a processor to that kind of work yourself, then pass the message to other camel endpoint.
I don't think current camel-cxf component can fit your needs.
Hope you are referring to SOAP with attachments (http://www.w3.org/TR/SOAP-attachments not just a SOAP message as MIME attachments.
I did, for time being, write a Processor which does limited job to progress with my POC but that isn't an implementation of SOAP with attachments. looking for some open source implementation of the same to use inside the processor if not a camel component exists.
Edited by: rchallapalli on Nov 12, 2011 11:45 PM
I too have the same issue with camel-http, as the external web service that I call using camel-http sends SOAP message with attachments.
I can not use CXF as the SOAP messages are RPC/encoded and CXF does not support RPC/encoded.
I too wrote a Processor but does not give me the content-types and this is the issue if we receive multiple attachments. If there is any component do let me also. I am also struggling with this issues.