From geronimo-dev-return-4033-apmail-incubator-geronimo-dev-archive=incubator.apache.org@incubator.apache.org Sat Oct 04 08:54:05 2003 Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 91161 invoked from network); 4 Oct 2003 08:54:04 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Oct 2003 08:54:04 -0000 Received: (qmail 45585 invoked by uid 500); 4 Oct 2003 08:53:32 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 45372 invoked by uid 500); 4 Oct 2003 08:53:31 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 45359 invoked from network); 4 Oct 2003 08:53:31 -0000 Received: from unknown (HELO hotmail.com) (207.68.163.133) by daedalus.apache.org with SMTP; 4 Oct 2003 08:53:31 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 4 Oct 2003 01:53:44 -0700 Received: from 144.139.159.217 by sea1fd.sea1.hotmail.msn.com with HTTP; Sat, 04 Oct 2003 08:53:44 GMT X-Originating-IP: [144.139.159.217] X-Originating-Email: [gianny_damour@hotmail.com] From: "gianny DAMOUR" To: geronimo-dev@incubator.apache.org Bcc: Subject: RE: [Deployment] IM #2 Summary for Directory Issue Date: Sat, 04 Oct 2003 10:53:44 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 04 Oct 2003 08:53:44.0664 (UTC) FILETIME=[045E2D80:01C38A55] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N From: "Jeremy Boynes" Date: Sat, 4 Oct 2003 00:50:19 -0700 >MBean persistence is used to store the configuration of each MBean (the >values of persistent attributes). This is used to reload the MBeans on >restart. The JSR77 state is not a persistent attribute, so all MBeans >come back in the STOPPED state. I see. So the "Persistence Service" snapshots the persistent attribute of an MBean. And the "Service Controler" snapshots the transient attributes, which are specific to the MBean state? What I had in mind was to add a persistent attribute to AbstractManagedObject abstracting the target state to reach when the server is restarted. This persistent attribute mirrors the transient state attribute and is persisted based on the installed persistence policy (which could be checkpoint, on attribute change et cetera). The mirroring of the transient state and the target state is broken when a request to shutdown the server is received. When a ManagedObject is restored, one uses this target state to trigger the relevant operation. One drawback I see in defining two services is that we will end up with two locations to be merged when the server is re-started. Moreover, it allows to share the persistence policy between these two services. >Given child objects can be stopped, I doubt startRecursive is the way to >go - instead, the controller will need to start each one individually >(and in the correct order). startRecursive is not the way to go to restore the identical state. However it will be the more simple to implement. Indeed, as you have underlined the controller will need to start in the right order the services. To start in the right order these services, this controller will need to re-implement a significant part of the DependencyService. I agree that the canStart method is a good template to implement such a feature. This is an academic exercice and also quite time consuming. Gianny _________________________________________________________________ Découvrez les nouvelles émoticônes animées de http://g.msn.fr/FR1001/866 MSN Messenger nouvelle formule