On Monday, February 13, 2012 2:45:04 AM Jens wrote: > > 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. > > Dan, > > thanks for that. Using a WSDL with a JMS binding does indeed make it work. > > Should I file a bug for this issue?
Yea. Please do so. That way it won't get lost. Attach your test case as well if possible. Thanks! -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
