Hi JP, There's no clean and simple way to do this right now with Ode. We've discussed it a few times on the mailing list (most notably here<http://markmail.org/message/7iozv6r55mprv3ej#query:JBI%20and%20correlation%20of%20MessageExchange%20ode+page:1+mid:gfxq2kpz4bgtpwiu+state:results>), however no concrete design has been proposed and nothing has been implemented towards supporting such implicit assignments (from the message to the process and back).
It's been on the project's wishlist for a while now and I've had discussions with Tammo van Lessen recently about getting it done sooner rather than later. You can contact me privately if you're interested in providing some form financial support for such effort. Design suggestions and patches are also very welcome :) I think your best alternative at this time would be to add explicit header assignments. alex On Thu, Jun 18, 2009 at 8:55 AM, <[email protected]> wrote: > Have already posted this to the user mailing list but on reflection expect > that the hard core technical heads on ODE would be better placed to comment. > > Currently on our project when external services invoke an ODE BPEL process > they provide a customised SOAP:Header in the web service call. The BPEL > process invokes other external web services as part of the business process. > My requirement is to pass the value from the inbound SOAP:Header request to > all external services that are invoked as a SOAP:Header. Ideally I want to > do this transparently without having to code mapping the data, particularly > as the value passed in is not business data and is required for all > services. > > Is using a custom MessageExchangeInterceptor together with using the > ode-axis2.mex.interceptors property the correct approach to solving this > problem? Any direction on the approach or other solutions greatly > appreciated. > > Thanks in advance, > James > > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the email by you is prohibited. >
