Logically a restart vs stop/start can make sense, but practically it may not depending on the service. The problem is a service has to be omniscient to understand how to transition old state to the new state and this can be nearly impossible if the service externalizes much of its functionality through customizable socket factories, etc.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 24, 2003 9:37 AM Subject: RE: [JBoss-dev] [ jboss-Change Notes-672538 ] Master Configuration Service > Well, then you cannot update the list of the JMX interceptors as you cycle > your service, right? Otherwise, how do you cycle the "ServiceContext" > interceptor? At one point, independently of where do you manage that, I am > pretty sure that you need a part of the system that thinks "I do think in a > specific way because it is a restart and not a definitive stop". You don't > think so? > > Cheers, > > > > sachay ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
