Thanks for your reply. Finally got it working. Is there any reason why the AddressHandler only supports onRecieve and onReply? In my use case the webservice expects an addressing header, most of the data to/from/action can be set at configuration time. The only thing that would need to be dynamic is the message id, and the handler already has an id generator. Instead of having to set the soap header properties, would it be possible to do something like
<code> <soap:ws-addressing to="to.address.com/to" action="action"> <!-- Optionally configure id generator --> </soap:-ws-addressing> </code> Thanks -- View this message in context: http://www.nabble.com/http-provider-binding-soap-headers-tf4691141s12049.html#a13497063 Sent from the ServiceMix - User mailing list archive at Nabble.com.
