Return-Path: Delivered-To: apmail-excalibur-dev-archive@www.apache.org Received: (qmail 62816 invoked from network); 19 Jun 2004 09:11:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Jun 2004 09:11:13 -0000 Received: (qmail 17597 invoked by uid 500); 19 Jun 2004 09:11:39 -0000 Delivered-To: apmail-excalibur-dev-archive@excalibur.apache.org Received: (qmail 17551 invoked by uid 500); 19 Jun 2004 09:11:38 -0000 Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Excalibur Developers List" Reply-To: "Excalibur Developers List" Delivered-To: mailing list dev@excalibur.apache.org Received: (qmail 17517 invoked by uid 99); 19 Jun 2004 09:11:37 -0000 Received: from [212.8.217.2] (HELO mail.s-und-n.de) (212.8.217.2) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 19 Jun 2004 02:11:37 -0700 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 7608A19F64C for ; Sat, 19 Jun 2004 11:10:56 +0200 (CEST) Received: from hw0386 ([192.168.2.31]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004061911013099-87947 ; Sat, 19 Jun 2004 11:01:30 +0200 From: "Carsten Ziegeler" To: "'Excalibur Developers List'" Subject: RE: [RT] Getting to the point of excalibur Date: Sat, 19 Jun 2004 11:10:27 +0200 Organization: S&N AG MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <07258F4244D6F649B1A78993D070B7CA01D4F427@ACSPMXE02> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-Index: AcRVOJky6Bsj+AqIQWm+6qNqQ87XGQApAn7w X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 19.06.2004 11:01:31, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 19.06.2004 11:01:32, Serialize complete at 19.06.2004 11:01:32 Message-ID: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hamilton Verissimo de Oliveira > > -----Mensagem original----- > De: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] Enviada > em: sexta-feira, 18 de junho de 2004 05:22 > > > Yes, I think dynamic lookup is one of the major advantages > of Avalon. > > You can decide at runtime which components you need. This is not > > possible with setter/constructor injection. > > Hmmm.. I think this is possible in a POJO world. Pico, for > instance, use component handlers and hints to (even) concrete > implementations. LSD can tell us more about that. > Hmm, no, I don't think so - but perhaps I'm really wrong. Imagine that you your implementation needs in some cases no service XY, in some cases one instance of it and in some rare cases two instances. If you are setter based, you only have one setXY() method, if you use a constructor you could have two arguments for the services there and then only use the amount of services you want, yes. But that looks a little bit ugly to me :) Of course the best examples come from Cocoon :) We build pipelines on a per request base, based on the called uri, the environment etc. Now, we have approx. 200 different pipeline components. Per request only approx 5 are assembled to build the pipeline. With a dynamic lookup mechanism you simply lookup the 5 components you need per request and combine them. And I think these scenarios are perfect areas for Avalon. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org For additional commands, e-mail: dev-help@excalibur.apache.org Apache Excalibur Project -- URL: http://excalibur.apache.org/