Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Stardust/Knowledge Base/Java API/Dynamic Event Binding"

(New page: ==  Requirements == A process let say Main Process has to trigger a sub-process called Escalation Process, but it doesn't know when to call it (not known during design). It only know...)
(No difference)

Revision as of 05:14, 6 September 2013

 Requirements

A process let say Main Process has to trigger a sub-process called Escalation Process, but it doesn't know when to call it (not known during design). It only knows that when certain data or indicator will be available at proces execution it would like to call the sub-process.

Approach

We will be modelling the Main Process by defining an Event Handling, Timer, and will not bind it Automatically. We will use a process data that will be set somewhere during process execution and this data will be used to indicate the time when we would like the Timer event to get fired and trigger the Escalation Process.


We will use IPP WorkflowService's API bindProcessEventHandler to bind the event after a value is available to the data to which Timer is bound.



Artifacts

Back to the top