All Implemented Interfaces:
Cloneable, Appendable
All Known Implementing Classes:
DefaultStateMachineModel
| Method from org.jboss.util.state.StateMachine$Model Summary: |
|---|
| acceptableStates, addState, addState, addState, clear, containsState, getCurrentState, getInitialState, getMappedState, isMappedState, removeState, setCurrentState, setInitialState, states |
| Method from org.jboss.util.state.StateMachine$Model Detail: |
|---|
|
Note, if the given state implements StateMachine.Acceptable then the final determiniation of its finality will be unknown until runtime. |
Existing acceptable states will be replaced by the given states. Acceptable states which are not registered as accepting states will be added as final states. If the acceptable set is null, then the added state will be final. Note, states are added based on the valid states which can be transitioned to from the given state, not on the states which accept the given state. For example, if adding state A which accepts B and C, this means that when the machine is in state A, it will allow transitions to B or C and not from C to A or B to A (unless of course a state mapping is setup up such that C and B both accept A). |
|
|
|
|
|
Since states with the same value are equivlent, this provides access to the actual state instance which is bound in the model. |
|
|
Does not need to validate the state, StateMachine will handle those details. |
Does not need to validate the state, StateMachine will handle those details. |
|