Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 94175 invoked by uid 500); 12 Nov 2001 16:39:32 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 94163 invoked from network); 12 Nov 2001 16:39:31 -0000 From: "Neeme Praks" To: , "Ovidiu Predescu" Cc: "Sylvain Wallez" Subject: RE: Interpreted sitemap Date: Mon, 12 Nov 2001 18:38:37 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N And to add one more comment: with the current approach in Avalon configuration handling, it is still possible to implement the Ant approach on top of this (write an AbstractReflectionConfigurable, override .configure(..) method to call the relevant methods using reflection and let other people just extend your class), while you cannot really use the Avalon approach if you would have based the whole system on reflection from the very beginning. So, I would say that Avalon approach is also more flexible :-) Neeme (also biased) PS this discussion is getting way too avalon specific for cocoon-dev... --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org