Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 89313 invoked by uid 500); 14 Nov 2001 20:53:26 -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 Delivered-To: moderator for cocoon-users@xml.apache.org Received: (qmail 32903 invoked from network); 14 Nov 2001 10:15:18 -0000 X-Originating-IP: [24.162.230.245] From: "Ryan Agler" To: cocoon-users@xml.apache.org Bcc: Subject: prevent cocoon:/xxx caching Date: Wed, 14 Nov 2001 05:15:31 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 14 Nov 2001 10:15:32.0009 (UTC) FILETIME=[4AC1D990:01C16CF5] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello~! I have a small problem that's driving me nuts Im wondering if anyone knows the answer to. In my sitemap, I have a pipeline (let's call it pipeline REF) with a serverpages generator that uses the "cocoon:" src attribute to reference a different pipeline (let's call it pipeline SRC) for its input source. Here's an example: parseParameters.xsp is a page I wrote that takes an XML document in a request parameter and converts it into contenthandler elements. This whole setup works PERFECTLY just ONE time, but then a file called SRC.java gets created in "work" in a directory called "http_" instead of "file_". Every request after the first one yields the exact same response -- i.e. cocoon doesn't know that the request parameters are different. How can I turn it off so that when I use cocoon:/SRC, that it won't get cached? Any ideas, or completely different workaround to achieve the same result would be appreciated 8-) _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: