Over 10 years of community discussion and knowledge are maintained here as a read-only archive.
<fsm initial="INITING"> <state name="INITING"}> <transition action="INIT_DONE" target="MODULE_INITING"/> </state> <state name="MODULE_INITING" changed="CHANGED_MODULE_INITING"> <transition action="MODULE_INIT_DONE" target="MODULE_PLAYING"/> </state> <state name="MODULE_PLAYING" changed="CHANGED_MODULE_PLAYING"> </state></fsm>
The problem is that my ChangedModuleInitingCommand initiates the transition to MODULE_PLAYING by sending a notification of CHANGE and type MODULE_INIT_DONE
... a mediator that is interested in both CHANGED_MODULE_INITING and CHANGED_MODULE_PLAYING. The problem is that my ChangedModuleInitingCommand initiates the transition to MODULE_PLAYING by sending a notification type MODULE_INIT_DONE, but then the mediator gets the CHANGED notifications in LIFO order, so it is actually in INITING state while it should be in PLAYING state.
maybe that implies that the two states should be combined into one?
1. What are the benefits in the case of SOA/MediaTurbine?
2. Any advice with this practice of chaining states without async break?