Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 76061 invoked from network); 6 Jan 2002 09:03:40 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Jan 2002 09:03:40 -0000 Received: (qmail 29776 invoked by uid 97); 6 Jan 2002 09:03:48 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 29585 invoked by uid 97); 6 Jan 2002 09:03:47 -0000 Mailing-List: contact avalon-dev-help@jakarta.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 avalon-dev@jakarta.apache.org Received: (qmail 29559 invoked from network); 6 Jan 2002 09:03:46 -0000 Message-Id: <200201060903.g0693jr08037@mail004.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Avalon Developers List" Subject: Re: One component, multiple configurations ... Date: Sun, 6 Jan 2002 20:00:12 +1100 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 4 Jan 2002 15:19, Taglang, Guillaume wrote: > Hi list, Hi there, > I've started to play around with Avalon, Phoenix and the other goodies. I > arrived to a point where I'm not able to find in the documentation what I'm > searching, so I have a small question: > > I have a generic component X which can have different behaviour for the > same ROLE depending on the configuration. I want to run different instances > of this component with different configurations. How could I achieve this ? Depends on what container you are working with. In most of the containers you can create multiple instances of the same type of component but with different names (and configurations). As they are the same type they implement the same interface (and thus have same Role) but the way they implement depends on whioch one you are working with. Alternatively you could create multiple different components that all implement the same interface (and thus have same Role) but are different actualt types. It really depends on how different the implementations are. Does this make sense ? -- Cheers, Pete ---------------------------------------------------------------- Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it. -- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982 ---------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: