Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 1971 invoked from network); 3 Feb 2004 22:18:49 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Feb 2004 22:18:49 -0000 Received: (qmail 23925 invoked by uid 500); 3 Feb 2004 22:18:17 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 23872 invoked by uid 500); 3 Feb 2004 22:18:16 -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 23798 invoked from network); 3 Feb 2004 22:18:16 -0000 Received: from unknown (HELO smtp.noos.fr) (212.198.2.115) by daedalus.apache.org with SMTP; 3 Feb 2004 22:18:16 -0000 Received: (qmail 17399 invoked by uid 0); 3 Feb 2004 22:17:19 -0000 Received: from unknown (HELO apache.org) ([212.198.17.4]) (envelope-sender ) by 212.198.2.115 (qmail-ldap-1.03) with SMTP for ; 3 Feb 2004 22:17:19 -0000 Message-ID: <40201EA8.8030105@apache.org> Date: Tue, 03 Feb 2004 23:20:24 +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: [RT][merlin] interoperability References: <07258F4244D6F649B1A78993D070B7CA0BB231@ACSPMXE02> In-Reply-To: <07258F4244D6F649B1A78993D070B7CA0BB231@ACSPMXE02> 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 Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote: > -----Mensagem original----- > De: Stephen McConnell [mailto:mcconnell@apache.org] > > >>Its all possible now - but it would be better to wait just a bit until >>the resolution of the model versus runtime is out of the way. > > > Hey, getting in the middle of this discussion, correct me if I'm wrong, the > process is: > > 1. Bootstraping Repository/Logging > 2. Build composition.data from a serialized data (or XML) > 3. build composition.model from data directives > 4. Assemble the composition.model.ContainmentModel (the tree) getting the > Appliances for any ComponentModel > 5. Init the components marked with activation="startup" > > Am I missing something? Nope - you not missing anything. This is a question concerning semantics of point 5. Currently when we deploy a component we invoke deploy against the runtime directly (the Appliance). Instead of this - the action of deploying needs to be applied to the model and its the model that then triggers an event which triggers a runtime adaption to the model state. Stephen. > > regards, > hammett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org > For additional commands, e-mail: dev-help@avalon.apache.org > > -- |------------------------------------------------| | 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