Hi James, Actually the intent of MessageExchangeInterceptor was primarily message throttling and flow control for inbound messages. So it's not even called for outbound. You could use it to limit the total number of active instances for a given process for example. But it has no knowledge of or correlation with outbound messages.
Inbound messages already have all the headers, what's missing for your scenario is a way to copy them to outbound messages. There's only one place in the engine where we're aware of outstanding requests and at least for now we don't check it before creating an outbound message. Additionally there's quite a bit of configuration we'd need to add to know which message should take its headers from which other message. Regards, Matthieu On Thu, Jun 18, 2009 at 3:45 PM, <[email protected]> wrote: > Hi Alex, > > Had a read of the link you sent and while I have to admit that I did not > understand all of the thread comments it certainly is in the same area of > the problem that I am trying to solve. One thing (there are others!!) that > confuses me is that the interface > org.apache.ode.bpel.intercept.MessageExchangeInterceptor is in the ODE code > base (think Matthieu and some of the other guys on the thread implemented > it) and from looking at the API looks like it is intended to serve my > purpose. Would appreciate if you could clarify why it is the wrong > approach. > > I would need a lot more time to be in a position where I think I could give > design suggestions.....Only just about to download the ODE source code! > > Will revert privately ~late next week on financial support after talking > with client (Intalio customer). > > Regards, > James > > > > > -----Original Message----- > From: Alex Boisvert [mailto:[email protected]] > Sent: 18 June 2009 19:02 > To: [email protected] > Subject: Re: Passing Custom SOAP Headers > > 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. > > > > > 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. >
