Return-Path: 
 <cocoon-dev-return-22727-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 31142 invoked by uid 500); 13 Feb 2002 22:25:00 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 31128 invoked from network); 13 Feb 2002 22:25:00 -0000
Message-Id: <200202132225.g1DMP5u29541@orion.rgv.hp.com>
X-Mailer: exmh 2.2 06/23/2000 with XEmacs 21.4.4 on Linux 2.2.19
From: Ovidiu Predescu <ovidiu@cup.hp.com>
To: Stefano Mazzocchi <stefano@apache.org>
Cc: cocoon-dev@xml.apache.org
Subject: Re: accessing request parameters in sitemap 
In-Reply-To: Your message of "Wed, 13 Feb 2002 22:06:59 +0100."
             <3C6AD573.3057BA90@apache.org>
X-Url: http://www.geocities.com/SiliconValley/Monitor/7464/
X-Image-Url: http://www.geocities.com/SiliconValley/Monitor/7464/ovidiu.tiff
X-Face: 
 ?(@Y~qjBA}~8ZMh5gM4{Q{bE_*:sCJ3@Z?{B*Co=J!#8bb~-z?-0._vJjt~MM59!MjxG%>U
 5>MW^2-\7~z04buszR^=m^U|m66>FdR@cFwhb;.A(8*D.QmLkK]z,md0'HiOE\pyeiv_PACR+P:Cm.
 wq_%l':E:q]g-UCc>r&s@BVo'kFN;(\9PF22Myg5w%nUBWQ6MJJ#qL#w>2oxckP'H:\$9F"mxsz]Dg
 k{1`fTcP'Y$CgGnc^paTV$dzhVX<SVN1RPb="gz3>+;(U$;Eb)P<>G)g)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 13 Feb 2002 14:25:05 -0800
Sender: ovidiu@orion.rgv.hp.com
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Wed, 13 Feb 2002 22:06:59 +0100, Stefano Mazzocchi <stefano@apache.org> wrote:

> Ovidiu Predescu wrote:
> > 
> > On Tue, 12 Feb 2002 13:58:19 -0500, "Vadim Gritsenko" <vadim.gritsenko@verizon.net> wrote:
> > 
> > > > From: ovidiu@orion.rgv.hp.com [mailto:ovidiu@orion.rgv.hp.com] On
> > > Behalf Of
> > > >
> > > > Currently the sitemap has a syntax which allows referring to matching
> > > > portions of the URL. Is there a way to refer to request arguments,
> > > > headers or session related properties directly in the sitemap?
> > > > Something like this:
> > > >
> > > > <map:match pattern="doc/**">
> > > >   <map:generate src="documents/{1}">
> > > >     <map:parameter name="type" value="{parameter(type)}"/>
> > > >     <map:parameter name="browser" value="{header(X-Browser)}"/>
> > > >   </map:generate>
> > > >   ...
> > > > </map:match>
> > >
> > > It can look like (not exactly, that's the hint):
> > >
> > > <map:match type="request-header" pattern="X-Browser">
> > >   <map:generate src="documents/xxx">
> > >     <map:parameter name="browser" value="{1}"/>
> > >   </map:generate>
> > >   ...
> > > </map:match>
> > >
> > > Check out matching and selection packages.
> > 
> > Right, but with this approach, I match on a request header, when what
> > I want is to still match on the URL, but access various parts of the
> > request.
> > 
> > With your example, I instead match on the request-header, and invoke
> > the pipeline with it. What should be the xxx in the documents/xxx?
> 
> What about using nested matchers?

Yep, sorry for not finishing this thread, Vadim came up with the same
thing in a private email yesterday. Nested matchers are what I was
looking for.

Thanks,
Ovidiu

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org