MainDeployer.shutdown undeploys the deployed packages in reverse order of
their deployment.  This cleans up the DeploymentInfo, UnifiedClassloaders,
and a bunch of other stuff.

ServiceController.shutdown just removes the mbeans, which leaves a lot of
stuff just sitting there.  IIRC I think it was causing problems when
MainDeployer shut down.  There was definitely a problem that caused me to
implement this behavior.

I suspect if we made DeploymentInfo into an mbean with appropriate
dependencies we could just do ServiceController.shutdown.  This would
probably fit better into a scheme of using mbean persistence to save state
across server shutdown and restart.

david jencks

On 2002.05.14 22:39:31 -0400 Jason Dillon wrote:
> Resending due to my messed up sendmail config...
> 
> ----------  Forwarded Message  ----------
> 
> Subject: ShutdownHook & MainDeployer.shutdown()
> Date: Fri, 10 May 2002 09:54:21 -0700
> From: Jason Dillon <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> 
> Can someone please explain to me why ServerImpl was changed to call
> MainDeployer.shutdown() in addition to ServiceController.shutdown()
> 
> --jason
> 
> -------------------------------------------------------
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We
> supply
> the hardware. You get the recognition. Email Us:
> [EMAIL PROTECTED]
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to