ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nowakowski, Mateusz" <Mateusz.Nowakow...@sabre-holdings.com>
Subject [ode1.1+fuse 3.2] deploy.xml process-events doesn't work
Date Fri, 19 Oct 2007 14:58:00 GMT
Thanks for the answer.

I have another issue regarding event listeners.
I need to filter launched filters and I've put:

    <process-events generate="none">

to my deploy.xml and all events are triggered, even when I put only 
<process-events generate="none"/> -- it behaves the same.

<?xml version="1.0" encoding="UTF-8"?>
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"         
        xmlns:xxx="http://xxx.xxx.pl ">

  <process name="sws:XxxProcess">
    <process-events generate="none"/>  

    <provide partnerLink="XXXRQ">

Mateusz Nowakowski

-----Original Message-----
From: Tammo van Lessen [mailto:tvanlessen@gmail.com] 
Sent: Friday, October 19, 2007 1:55 PM
To: user@ode.apache.org
Subject: Re: Difference between ode ActivityEnabledEvent and


2007/10/19, Nowakowski, Mateusz <Mateusz.Nowakowski@sabre-holdings.com>:
> What is the difference between ActivityEnabledEvent and
> ActivityExecStartEvent ? In javadoc for first one I written: "Event
> when the parent activity or process enables this activity." And for
> second one: "Event sent when the <em>body</em> of the activity starts
> executing."
> What is performed between these events ?
The ActivityEnabledEvent is raised when the parent structured activity
has been invoked and has created this certain activity. It is so to
say ready for execution.

The ActivityExecStart event is only raised when the join condition of
the activity is successfully evaluated to true. That means that the
actual execution of this activity starts.

> I presume that ActivityExecStartEvent is lauched by activity itself in
> the beginning of activity. But is it possible situation that
> ActivityEnabledEvent is launched, but ActivityExecStartEvent isn't ?
Yes, this might be the case if an activity's join condition was
evaluated to false or the activity has been disabled due to dead path
elimination. This situation basically means: The navigator has been
aware of this activity but has decided to not execute it due to some
unsatisfied preconditions.


Tammo van Lessen - tvanlessen@gmail.com - http://www.taval.de

View raw message