Hi David The best example I have right now is JSR-77. Because the JSR-77 management components are shadow MBeans of offer JBoss components they have to be created when the JBoss MBean is created and destroyed when its master get destroyed.
But as you know JBoss components are not finally set until there attributes are set (otherwise we would have to use the unnamed constructor arguments). Therefore JSR-77 creation cannot rely on the creation of the MBean component but must rely when the MBean is finally set. Therefore I need the init() method to have a point where the MBean is set and I can create the JSR-77 component. You may ask why not create in the start() method but JSR-77 components allows the administrator to start AND stop the component behind it. If now the creation of the JSR-77 component is in start() and the destruction in stop() I am not able to restart the JSR-77 component (and then as well as the JBoss component). Andy ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 11, 2001 10:14 AM Subject: Re: RE: [JBoss-dev] (rh) startup levels proposal and questions. > Maybe you could give a specific example of why the 2 stage startup is useful. Even Rickard said the "init" step should not refer to anything outside the mbean being inited. I can't see any way the mbeans can distinguish 1,2,3, or 17 stage startup if only the last can refer to other mbeans. Are you using this to hide dependencies between mbeans? > ______________________________________________________________________ > View this jboss-dev thread in the online forums: > http://jboss.org/forums/thread.jsp?forum=66&thread=5378 > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
