Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Works as Designed
-
Affects Version/s: 2.2.1
-
Fix Version/s: None
-
Component/s: Core: Flow Executor
-
Labels:
Description
When more than one action is configured into the same action state, the second action is not executed, resulting in failures further down the web-flow food chain.
<action-state id="doSomething"> <set name="flowScope.name" value="service.findName(someValue)"/> <set name="flowScope.address" value="service.findAddress(someotherValue)"/> <transition to="doSomethingElse"/> </action-state>
We would like to see the typical Programmer Error when this happens, which would be consistent with how you handle no set actions being configured.
We do have the following work-around.
<action-state id="doSomething"> <on-entry> <set name="flowScope.name" value="service.findName(someValue)"/> </on-entry> <set name="flowScope.address" value="service.findAddress(someotherValue)"/> <transition to="doSomethingElse"/> </action-state>