Hi Daniel
So that fixed part of my issue, but not sure if it brought me steps forward or
back.
So now when I add the swa bindings to the WSDL and regenerate, I do see a data
handler argument now instead of a byte[] argument, however now the outgoing
soap requests have the binary content in
I think you are confusing a couple of specs…..MTOM and Soap W/ Attachments
are actually two separate specs and are handled differently.
For SwA, you wouldn’t turn on MTOM. CXF should be able to look in the WSDL
and as long as mime things are properly and completely defined in the
So here's something of interest - I think some of the behavior has to do with
how the MTOM field is defined. Most examples, including the one used by CXF
have it as a field within a request object. in my case, the SOAP service is
exposing the MTOM attribute as a separate argument. this is
Hi,
I'm looking to integrate with an existing webservice that uses attachments
for its handling of binary content. I've enabled mtom on my client. I've
tested the service using SoapUI and I can see that it properly handles the
attachment when using the attachment option in SoapUI.
When I try
