ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: Monitoring
Date Tue, 18 Dec 2007 22:23:32 GMT
As of today, there's no facility in the integration layer to create a
context that's longer than a single message exchange.  The engine has larger
contexts (process, scopes, partnerLinks) but these are not yet exposed in
the IL.  That's something we plan to address in the medium term (next 3-4
months, I guess), probably by allowing named context to be associated with
message exchanges.

Right now, the only (portable) ways to carry context between message
exchanges is to add custom message headers and explicitly map between them,
or use BPEL correlations.


On 12/18/07, Björn Hagemeier <b.hagemeier@fz-juelich.de> wrote:
> Hi all,
> we're using Ode to orchestrate services in the ServiceMix JBI
> environment. This is working ok and we're able to send Ode events to a
> monitoring component on the bus. This is done via OdeEventListener
> hooked into the deployed Service Engine. In order to track groups of
> events belonging to the same process, we attach a property to the
> message exchange that initiates the process instance. So far so good.
> Now my observation: the property attached to the message still exists
> and is propagated to our monitoring component with each OdeEvent. This
> works exactly until the first BPEL »invoke«, which still contains our
> property. All following events don't carry the property anymore, but we
> would have expected them to. Does anyone on the list have an idea what
> we can do about it?
> Best regards,
> Björn

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message