Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 55686 invoked by uid 500); 26 Mar 2002 13:32:51 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 55667 invoked from network); 26 Mar 2002 13:32:50 -0000 Message-ID: <3CA07603.8080301@anyware-tech.com> Date: Tue, 26 Mar 2002 14:22:11 +0100 From: Olivier Rossel User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; fr-FR; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: fr-fr MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Power using the sitemap. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Here is my problem: i have several similar directories structures containing XML datas, for each customers I have (customer1/, customer2/, customer3/) I need to apply the same pipeline on one directory tree, depending on a request parameter: when I have "URL?customer=IBM", i need my pipeline to get infos from somewhere inside the customer1/ directory when I have "URL?customer=Microsoft", i need my pipeline to get infos from somewhere inside the customer2/ directory. I wonder how I can get that. I tought about an action that sets a variable {customerRoot} depending on the request parameter "customer". And my pipeline builds all its URLs using this variable. Or a pipeline that matches any pattern, tests the requestparameter with a selector and makes a "map:read" to an internal pipeline, and with a "src" containing the good customerRoot string Or a session-parameter set by I do now know who :-) I presume that pointing to a different directory structure depending on a parameter is classic. I just would like to know which option you would use. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: