Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 51937 invoked from network); 6 Apr 2004 07:02:27 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Apr 2004 07:02:27 -0000 Received: (qmail 6993 invoked by uid 500); 6 Apr 2004 07:01:59 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 6939 invoked by uid 500); 6 Apr 2004 07:01:59 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 6924 invoked from network); 6 Apr 2004 07:01:59 -0000 Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by daedalus.apache.org with SMTP; 6 Apr 2004 07:01:59 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id BBB1519F609 for ; Tue, 6 Apr 2004 09:02:10 +0200 (CEST) Received: from hw0386 ([10.10.2.54]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004040608553837-32539 ; Tue, 6 Apr 2004 08:55:38 +0200 From: "Carsten Ziegeler" To: Subject: RE: [Kernel22] How to develop a component? Date: Tue, 6 Apr 2004 09:04:30 +0200 Organization: S&N AG MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <4071DC8A.9050203@apache.org> Thread-Index: AcQbW9afz7OLXh9/QR2NIjeaiDAgXwASSJCg X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 06.04.2004 08:55:38, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 06.04.2004 08:55:38, Serialize complete at 06.04.2004 08:55:38 Message-ID: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" 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 Stefano Mazzocchi wrote: > > Carsten Ziegeler wrote: > > > I'm trying to figure out what the current kernel already > provides and > > what not. > > > > Let's forget all the xml (descriptors etc) for a moment. Imagine I > > want to write a block, that provides - let's say a special file > > generator - that can be used in other blocks (in my app block). > > > > Now, obviously this generator will implement our Cocoon > Generator interface. > > What else does the kernel already provide for the component > lifecycle? > > (Logging, Configuration etc.) > > > > Or is this a to discuss/do? > > I guess it's a to-do/to-discuss. > > The block design didn't deal with component lifecycle because > that's another concern (and, originally, it was supposed to > be taken care of by avalon). > Ok. > I don't know Pier's ideas about this. > > I think it's a good time for cleaning up what avalon did > wrong, simplify as much as we can and tune it for our needs. > > But I'm wide open to suggestions, as long as we move away from avalon. > :) Sounds good to me. Now what do you think of using the things from Avalon that are good (for us)? Now, I think, some of the interfaces (for logging, contextualization, initialization) are good and we could directly use them instead of building just a clone of them. The only interface which could be better is Serviceable/Composable where the lookup is done using a plain String. There we should use something like lookup(Interface, Hint). WDYT? Carsten