Hmm, now I see you are asking if "stop all without undeploy" is useful. I don't think so: it is very apt to interfere with the stopping/restarting of mbeans based on their mbean-ref dependencies. In particular, unless you stop mbeans in the reverse order of their deployment (actually startup), some will stop others. I don't think this order is accessible.
Most of our mbeans don't actually implement stop properly (so they can be restarted). I can't think of any reason to stop all the mbeans without stopping the server. david jencks On 2001.11.13 17:12:36 -0500 Jeff Tulley wrote: > Hey all, > I just ported the old 2.4.x version of Stop.java over to Rabbit Hole, > then realized that there is a Shutdown.java command that actually does a > full shutdown. So, before I chuck the "new" version of Stop.java as a > "fun academic exercise", I was wondering if the stop functionality is > needed and/or useful. The old Stop.java did not perform a full shutdown, > but instead stopped each of the MBeans. Not being a JBoss power user > (yet?), I do not know if such stop functionality is every really useful. > > The version I had was updated to use the RMIAdaptor instead of the old > JMXAdaptor. > > Keep (and submit as a patch) or scrap it? > > Regards, > > Jeff Tulley ([EMAIL PROTECTED]) > (801)861-5322 > Novell, Inc., the leading provider of Net services software. > > > _______________________________________________ > 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
