Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 1831 invoked by uid 500); 29 Jan 2003 15:47:47 -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 1776 invoked from network); 29 Jan 2003 15:47:45 -0000 Date: Wed, 29 Jan 2003 16:45:25 +0100 To: cocoon-dev@xml.apache.org Subject: Re: input module question Message-ID: <20030129154525.GE4697@bremen.dvs1.informatik.tu-darmstadt.de> Reply-To: haul@informatik.tu-darmstadt.de References: <20030129135616.GD4697@bremen.dvs1.informatik.tu-darmstadt.de> <0EBC4E27-339C-11D7-9FAB-0003935AD2EE@media.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0EBC4E27-339C-11D7-9FAB-0003935AD2EE@media.demon.co.uk> Organization: Databases and Distributed Systems Group, Darmstadt University of Technology User-Agent: Mutt/1.5.3i From: Christian Haul X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On 29.Jan.2003 -- 03:12 PM, Jeremy Quinn wrote: > >The snippet above would (currently) be located in cocoon.xconf and the > >lookup process would be hidden from a sitemap designer's point of > >view. To the designer, it would be just {foo:bar}. > > So (forgive me if I have misunderstood this again) .... the setup that > says "the value of sitemap-param-1 is used to map to a node's name in > XMLFileModule" resides globally in Cocoon.xconf, not in the sitemap? > > Would this not mean that this module setup could not be re-used in a > different but similar matcher/pipelines where the key-word comes > through in a different sitemap=param-#? Indeed, this would be the case. We are not able to pass more than the attribute name to the module (from sitemap, that is). Thus it would be hardwired to a sitemap parameter :-| IOW different instances would be necessary if different sitemap parameter names are needed. Of course we could aim at passing more than one parameter to it using a HTTP GET like syntax. Chris. -- C h r i s t i a n H a u l haul@informatik.tu-darmstadt.de fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org