Consider extending of ModuleInstance with end(), suspend() a

[p4elka]

Now it is not possible to get notification about process instance end, suspend or resume in module instance associated with the process instance. Sometimes it is required in order to perform additional logic in external modules.
As an example we could look at JBPM built in module instance TaskMgmtInstance, which already get's notified about process instance end, suspend and resume using custom methods and additional logic in token class. (on process instance end removeSignalling(token) method gets called, on suspend/resume suspend(token)/resume(token) method is called)

So as a solution end/suspend/resume methods of token might be changed and notification might be send to all registered module instances. We probably need per token notification, so that all possible requirements could be fullfilled i.e TaskMgmtInstance requires exactly per token notification, in our application we need only process wide notification.

What do you think ?

[kukeltje]

search the fine jira

[p4elka]

Do you mean that there is already JIRA issue created about the subject ? I cannot find anything related. If you know specific issue, could you please paste a link here ?

[kukeltje]

In this forum:

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76733

first hit in google:

http://www.google.nl/search?q=jira+suspend+event+jbpm

[p4elka]

Hmm, I do not really want this to be supported through events. Actually suspend and resume is not of a big interest to me, currently I do care about process instance end. And there is already a 'process-end' event, but in order to be notified about the event inside my module instance, I need to create runtime action and register it in process instance. Runtime action needs to be associated with action + delegation, and the problem is that action will be persisted on process instance save and I do not want to create any additional database records. All I need it simply lightweight notification about the fact that process instance is ended, so I could do necessary 'finalization' actions in my module instance, same way it is now now in TaskMgmtInstance, imagine if TaskMgmtInstance notification would be implemented using events and I do not see reasons why built-in module instances should be handled differently then custom ones, at least in this area.

[kukeltje]

ahhhhh.... now that is (to me, non-native english speaker) a much more clear explanation....

What I do not understand why you need to configure runtime actions. Events are very flexible.

[p4elka]

Hmm, how do I listen for an event without some action registered for an event - either action defined in processdefinition.xml or runtime action ? Could you please give an example or just hint ?

Thanks !
Olga, another non-native speaker :)

[kukeltje]

just something like

<process-definition>
<event type="myEvent" class="myClass">
.... params etc can go here
</event>

...

</process-definition>

and then just send a 'myEvent' anywhere...