[SOA-2010] Conditional transition cannot be considered as a default one - JBoss Issue Tracker

XML

Word

Printable

Release Notes Text:

Hide
https://issues.jboss.org/browse/SOA-2010

The software was erratic in terms of support for transitions. It has been changed so that, if no condition is met, the default transition is taken. (The default transition is the first unconditional transition if there is one, or else the first conditional transition.) If only conditional ("guarded") transitions are available, and none of the conditions on the transitions evaluate to true, an exception will be thrown. Throwing an exception when none of the guarded transitions are viable informs the user that the process is incorrect.

Show
https://issues.jboss.org/browse/SOA-2010 The software was erratic in terms of support for transitions. It has been changed so that, if no condition is met, the default transition is taken. (The default transition is the first unconditional transition if there is one, or else the first conditional transition.) If only conditional ("guarded") transitions are available, and none of the conditions on the transitions evaluate to true, an exception will be thrown. Throwing an exception when none of the guarded transitions are viable informs the user that the process is incorrect.
Release Notes Docs Status:
Documented as Resolved Issue

See the linked issue.

cloned from

JBPM-3213 Conditions on transitions can be used leaving all nodes -- inconsistent behaviour

cloned to

SOA-2858 Conditional transition cannot be considered as a default one

is blocked by

JBPM-2834 Node.getDefaultLeavingTransition returns null when there is no unconditional transition

is related to

JBIDE-8956 Make Conditional Transitions Illegal if they are Leaving a Node that is not a Decision Node

SOA-1979 [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition