cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <h...@informatik.tu-darmstadt.de>
Subject Re: request:requestURI vs requestURI:requestURI
Date Thu, 09 Oct 2003 23:02:14 GMT
Sonny Sukumar wrote:
> 
>> From: "Horsfield, Peter A." <peter.horsfield@ngc.com>
>>
>> > Assuming these things, I'd like something that returns
>> > the request URI along with the full query string.
>>
>> Use RequestModule
>>
>> Try:
>>
>>     {request:/requestURI}
>>
>> I've not personally done this, but it seems logical.
> 
> 
> Hmm, why the "/"?  I assume that has something to do with JXPath?  Btw, 

yes. but it's not needed.

> do all input modules use JXPath?  I'm new to using input modules and 

no, only some do. should be indicated in their javadoc. if not, see 
which inherit from AbstractJXPathInputModule

> If it doesn't
> 
>> return the query string you might be able to use
>>
>>     {request:/requestURI}?{request:/queryString}
> 
> 
> Can I use any "get" method in interface Request by removing the "get" 
> and making the first letter of the first word lowercase?  For example: 
> "getRequestURI" --> requestURI", "getQueryString" --> "queryString", etc.

more or less, yes.

> In general I understand what you're saying with the last example, but 
> the "/" again puzzles me since I'm not sure of its purpose.

think XPath.

	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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message