Hi Geeks Because JSR-77 are only a "shadow" objects of the real JBoss components the JBoss MBean life-cycle must not interfere with the StateManageable interface.
Therefore two steps are made: - start() and stop() method of the State Manageable objects are internally renamed to mejbStart() and mejbStop() - when a JSR-77 component is started / stopped it does only deal with its own life-cycle but does not perform start() / stop() on its target (JBoss component). I created a new class "StateManagement" which contains the state management of StateManageable components but it does not start() or stop() the JSR-77 components because it does only inform the JSR-77 client that a state has changed. Now when a JSR-77 client class "stop" method the JSR-77 component will call "stop" on the JBoss component which will send a STOPPING / STOPPED notification. These notifications will be picked up by the JSR-77 component (in fact by StateManagement) and then sent as a JSR-77 event to the JSR-77 client (if registered). The same is true for "start" and "startRecursive". When a JBoss component is stopped or started outside of JSR-77 the JSR-77 component will pick up the notifications (if state is managed) and send the same JSR-77 events to the JSR-77 client. Have fun xxxxxxxxxxxxxxxxx Andreas Schaefer Senior Consultant JBoss Group, LLC xxxxxxxxxxxxxxxxx _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
