Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 49145 invoked from network); 11 Mar 2004 08:12:38 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Mar 2004 08:12:38 -0000 Received: (qmail 88617 invoked by uid 500); 11 Mar 2004 08:12:15 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 88378 invoked by uid 500); 11 Mar 2004 08:12:14 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 88363 invoked from network); 11 Mar 2004 08:12:14 -0000 Received: from unknown (HELO smtp.noos.fr) (212.198.2.118) by daedalus.apache.org with SMTP; 11 Mar 2004 08:12:14 -0000 Received: (qmail 12475 invoked by uid 0); 11 Mar 2004 08:12:24 -0000 Received: from unknown (HELO apache.org) ([212.198.17.4]) (envelope-sender ) by 212.198.2.118 (qmail-ldap-1.03) with SMTP for ; 11 Mar 2004 08:12:24 -0000 Message-ID: <40502026.3020601@apache.org> Date: Thu, 11 Mar 2004 09:15:34 +0100 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: More "academic" ideas [Was: [VOTE] New sandbox project] References: <20040311054200.69DF424B52E@mail.ibiblio.org> In-Reply-To: <20040311054200.69DF424B52E@mail.ibiblio.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 J Aaron Farr wrote: > > ...... Original Message ....... > On Wed, 10 Mar 2004 13:33:13 -0700 "Jonathan Hawkes" > wrote: > >>>- Concerns like Creation/LogEnabling/Service/Initialize should have a >> >>order >> >>>of execution. >> >>They do. Concerns are evaluated in the order they are added to the >>container. >> > > > I agree. I think this would be a simplier and more natural method. It > would also allow for the user to customize the lifecycle easily. > > But what about shutdown lifecycles? There would need to be a distinction. Just a thought - instead of looking at "shutdown" as a Concern within a queue, I figure one should adding a Startable concern - where the concern handles deployment and undeployment (starting and stopping respectively) in a sequence with other concerns. Cheers, Steve. -- |------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------| --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org