Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 7311 invoked from network); 5 Apr 2004 13:27:32 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Apr 2004 13:27:32 -0000 Received: (qmail 15826 invoked by uid 500); 5 Apr 2004 13:27:23 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 15762 invoked by uid 500); 5 Apr 2004 13:27:22 -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 15741 invoked from network); 5 Apr 2004 13:27:22 -0000 Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by daedalus.apache.org with SMTP; 5 Apr 2004 13:27:22 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 5B68519F58E for ; Mon, 5 Apr 2004 15:27:23 +0200 (CEST) Received: from hw0386 ([10.10.2.54]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004040515205235-30364 ; Mon, 5 Apr 2004 15:20:52 +0200 From: "Carsten Ziegeler" To: "Cocoon-Dev" Subject: [Kernel22] How to develop a component? Date: Mon, 5 Apr 2004 15:29:42 +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 Thread-Index: AcQbEg0svqxSSreqQ6yyVc08BIQo4Q== X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 05.04.2004 15:20:52, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 05.04.2004 15:20:53, Serialize complete at 05.04.2004 15:20:53 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 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? Carsten