Clarification: jBPM4 activities and events

[heiko.braun]

The javadocs of the ActivityBehaviour [1] interface states:

* <p>Activities can be used to implement the behaviour of activities, in
* which case this behaviour is associated to a graphical activity in the diagram,
* or they can be added as events, in that case, they are being hidden from
* the diagram.

What's the relationship between activities and events in this case?

[1] http://jbpm.dyndns.org/jbpm4/jbpm-api/apidocs/org/jbpm/activity/ActivityBehaviour.html

[kukeltje]

uuhhhhmm..... I'd say none? Besides that the thing that happens (is executed) is based on the same java interface? (have not worked with it, but it sounds like it is similar to what jBPM 3 does)

[tom.baeyens]

javadoc of the execute method was updated to:

piece of Java code that is to be included in a process as activity behaviour or as a hidden listener to process events.

ActivityBehaviour's can be used to implement the behaviour of activities, in which case this behaviour is associated to a graphical activity in the diagram.

An ActivityBehaviour can control the propagation of execution. ActivityBehaviour's can become external activities when they invoke ActivityExecution.waitForSignal(). That means the activity will become a wait state. In that case, ExternalActivityBehaviour should be implemented to also handle the external triggers.

activities should not be used for listening to events. EventListener should be implemented.

is that better ?

[heiko.braun]

yes, thanks ;)

[kukeltje]

I see I've got a lot of catching up to do... time... time... time...