Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 5155 invoked from network); 16 Jul 2004 08:46:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Jul 2004 08:46:16 -0000 Received: (qmail 89498 invoked by uid 500); 16 Jul 2004 08:46:11 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 89411 invoked by uid 500); 16 Jul 2004 08:46:10 -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 89387 invoked by uid 99); 16 Jul 2004 08:46:10 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [81.56.241.65] (HELO mail.anyware-tech.com) (81.56.241.65) by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 16 Jul 2004 01:46:06 -0700 Received: from [10.0.0.183] (unknown [10.0.0.183]) by mail.anyware-tech.com (Postfix) with ESMTP id BB1165EC24; Fri, 16 Jul 2004 10:46:04 +0200 (CEST) Message-ID: <40F795CC.8040206@apache.org> Date: Fri, 16 Jul 2004 10:46:04 +0200 From: Sylvain Wallez User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: fr, en, en-us MIME-Version: 1.0 To: dev@cocoon.apache.org Cc: lenya-dev@cocoon.apache.org Subject: Re: [RT] Virtual Sitemap Components References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Andreas Hartmann wrote: > Carsten Ziegeler wrote: > >> I want to start the implementation of the virtual sitemap components >> in the next weeks; but before, we should discuss how they will look >> like :) >> >> The first point - and imho most important point is, of which components >> a virtual sitemap component (VSC) can be assembled. >> My understand is that a VSC is either: >> - a generator followed by one or more transformers >> - a set of transformers >> - a set of transformers followed by a serializer >> Thus, the VSC acts like a generator, a transformer or a serializer. > > > Sorry for cross-posting, but this could maybe address a concern > Lenya is faced with. > > The scenario is as follows: > > Lenya provides so-called "CMS screens". This is a simple transformation > to create the Lenya look-and-feel forms, error messages etc. > > It is done using a meta stylesheet approach triggered by > > > > The problem is that we would like to add a i18n step to this > transformation, which would be quite difficult (if not impossible) > to implement using a meta stylesheet. We don't use a resource > because we need to access the transformation from a lot of sitemaps. > > My question is: Could VSCs be declared in the sitemap? For instance: > > > > > > > > > > > > Is this a possible scenario for the VSC concept? Exactly. > I think an important questions is how to pass parameters to a VSC and > how to distribute them to the single components. Passing parameters to a VSC is very similar to passing parameters to resources. There's however a special handling of the @src attribute that exists on generators and transformers, which does not exist on resources. Example: Definition (syntax and exact location still has to be defined): Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }