Oct 26th, 2005, 03:32 PM
Suggestion to correct the entry/exit state behavior
Right now when I specify the <entry> or <exit> behaviors during the state definition, they would execute an action, but regardless of its status continue on the execution of the state. When looking at the implementation, such a state gets an Entry/ExitAction set as a CompositeAction which takes inside the newly created AnnotatedAction object which is indeed being called to execute whatever it is you've specified.
Looking at the CompositeAction i see a property which indicates if it should stopOnError. But there is no way to indicate if the newly created CompositeAction object that wraps my entry/exit behaviors should stop if the <entry> action returns an error Event in response.
Could the change be made to the XmlFlowBuilder to accept a property element that would allow us to specify if we want an <entry> stopOnError and what that errorEventId should be instead of just doing a state.setEntryAction(new CompositeAction(parseAnnotatedActions(entryElement ))); call.
Oct 26th, 2005, 08:41 PM
You may add a request for enhancement on JIRA.
Oct 28th, 2005, 04:25 AM
It's unlikely that we'll add this. At the moment our position is: things like entry and exit action, but also transition actions, allow limited or no controll over the flow. If you want full flow controll, just execute that particular action in an action state.