GrailsFlow

Wait nodes in front of OrJoin

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.0.12
  • Component/s: None
  • Labels:
    None
  • Request Controller:
    Albers, Stephan
  • External Supervisor:
    Voitovich, Mary
  • Executing Programmer:
    Please select

Description

When an OrJoin node has two or more wait nodes (or other node types) in front, all nodes other nodes in front of the OrJoin should be stopped/finished, after the first node activates the OrJoin.

Example process:

start(isStart: true) {
action {Log(logMessage: 'start') return okay() }
on('okay').to(['wait1', 'wait2'])
}

wait1Wait() {
action {Log(logMessage: 'wait-1')}
on('okay').to(['final'])
}

wait2Wait() {
action {Log(logMessage: 'wait-2')}
on('okay').to(['final'])
}

finalOrJoin(isFinal: true) {
action {Log(logMessage: 'final')}
}

When coming from Wait1 into OrJoin, Wait1 status is COMPLETE but Wait2 is still ACTIVATE.

Activity

Hide
Antonicheva, July added a comment - 14/Jun/11 10:05 AM - edited

The problem was solved from the plugin version 'grailsflow-core-1.0-20100603'. Currently developed versions - 'grailsflow-core-1.1-SNAPSHOT' and 'grailsflow-core-1.0.12-SNAPSHOT' contain changes.

Show
Antonicheva, July added a comment - 14/Jun/11 10:05 AM - edited The problem was solved from the plugin version 'grailsflow-core-1.0-20100603'. Currently developed versions - 'grailsflow-core-1.1-SNAPSHOT' and 'grailsflow-core-1.0.12-SNAPSHOT' contain changes.

People

Vote (0)
Watch (0)

Dates

  • Created:
    16/Sep/09 8:55 PM
    Updated:
    24/Feb/12 8:47 AM
    Resolved:
    24/Feb/12 8:47 AM