On Friday, February 10, 2012 1:44:16 AM Jens wrote: > >> On Friday, February 03, 2012 7:46:30 AM Jens wrote: > >>> does CXF (2.5.2) still support SwA? > >> > >> It should be working. We have tests for it and the JAX-WS TCK requires > >> it.
> Is it possible that this error is a side effect of trying to use SwA with > the JMS transport? I've tried to remodel the test case to use HTTP for > easier testing but in this case the message comes out in MIME format as > expected. Yes and no. The issue is that the WSDL is claiming an HTTP transport, but you are setting a JMS transport. When this happens, internally, a few things get reset to defaults and, in this case, the attachments are lost. Unfortunately, I'm not really seeing any way of working around the issue right now. :-( The only thing you can do is copy _bind/BindingHTTP.wsdl to _bind/BindingJMS.wsdl, update the tranport string in there and change the name of the binding, and update the service entries to include a JMS port. That should allow it to work fine. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
