Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 1389 invoked by uid 500); 11 Jul 2001 13:50:32 -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 1345 invoked from network); 11 Jul 2001 13:50:24 -0000 From: "Torsten Curdt" To: Subject: RE: request info action Date: Wed, 11 Jul 2001 15:49:58 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-reply-to: X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > > > > But I have been wondering a couple of times... > > > > > Shouldn't there be some common standard parameter > > > > > available in the substitution map?! Like: > > > > > > > > > > - requested uri > > > > > - servlet context or base-uri > > > > > - query parameters > > > > > > > > > > Or is an action the better and cleaner way to go? > > > > > > > > i'm _all_ for being able to access this data via the > > substitution map. > > > > occasionally, i want to be able to use a request parameter in > > > > the sitemap > > > > but i can't. > > > > > > Definitely - I'd also like POST parameters too! > > > > For the POST parameter there is already the RequestParamAction. > > > Torsten > > Darn - I really *must* keep uptodate! > > Could this not be extended to cope with GET params? Should work for GET as well! -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org