Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 65634 invoked by uid 500); 14 Mar 2002 08:15:12 -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 65623 invoked from network); 14 Mar 2002 08:15:11 -0000 From: "Carsten Ziegeler" To: "Cocoon-Dev" Subject: [Vote]: Where to define the sitemap components? Date: Thu, 14 Mar 2002 09:17:22 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 14.03.2002 09:15:22, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 14.03.2002 09:15:23, Serialize complete at 14.03.2002 09:15:23 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Team, I'm still not convinced that it is a good idea to have some components (generators, transformers etc) of the sitemap defined in the cocoon.xconf and some in the map:components section of the sitemap. We will confuse many users with this, believe me. There will be many complains that for example the file generator isn't available any more, as it is not visible in the sitemap. So for a forthcoming release, I propose to move them back into the sitemap and after the release we can think of a better way of defining components. Thoughts? Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org