[jboss-jira] [JBoss JIRA] Updated: (JBMAN-51) Expose runtime state from ManagedComponent

Expose runtime state from ManagedComponent ------------------------------------------ Key: JBMAN-51 URL: https://jira.jboss.org/jira/browse/JBMAN-51 Project: JBoss Managed Issue Type: Feature Request Components: managedobject Affects Versions: JBossMan.2.0.0.GA Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossMan.2.1.0.CR1 Related to JBAS-5523, the ManagedComponent view needs to have some notion of a runtime state. A reasonable set of states seems to be the JSR77 STARTING (0) This state indicates that the SMO has been requested to start, and is in the process of starting. On entering this state an SMO may generate an event whose type value is "j2ee.state.starting". Event noti?cation of the STARTING state is optional for all managed objects that implement StateManageable. RUNNING (1) This is the normal running state for an SMO. This state indicates that the SMOisoperational.OnenteringthisstateanSMOmustgenerateaneventwhose type value is "j2ee.state.running". Event noti?cation of the RUNNING state is required for all managed objects that implement StateManageable. STOPPING (2) This state indicates that the SMO has been requested to stop, and is in the process of stopping. On entering this state an SMO may generate an event whose type value is "j2ee.state.stopping". Event noti?cation of the STOPPING state is optional for all managed objects that implement StateManageable. STOPPED (3) This state indicates that the StateManageable Object has stopped and can be restarted.OnenteringthisstateanSMOmustgenerateaneventwhosetypevalue is"j2ee.state.stopped".Eventnoti?cationoftheSTOPPEDstateisrequired by all managed objects that implement StateManageable. FAILED (4) This state indicates that the StateManageable Object has unexpectedly stopped. On entering this state an SMO must generate an event whose type value is"j2ee.state.failed".Eventnoti?cationoftheFAILEDstateisrequiredby all managed objects that implement StateManageable. It may be possible to start an SMO that has entered the FAILED state by calling thestart() operation. It maybepossibletostopanSMOthathasenteredtheFAILEDstatebycallingthe stop() operation. An SMO that cannot succesfully reach the RUNNING or STOPPED state from the FAILED state must reenter the FAILED state after the the attempt to reach the RUNNING or STOPPED state fails and emit another "j2ee.state.failed" event. An SMO that cannot succesfully reach the RUNNINGorSTOPPEDstatefromtheFAILEDstaterequiresintervention,such as redeployment, to restore the managed object to the desired state.