cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Horsfield, Peter A." <>
Subject RE: request:requestURI vs requestURI:requestURI
Date Thu, 09 Oct 2003 18:29:49 GMT
Hey Sonny,

Sorry it didn't end up clear.


the first, and differing, part can be any name that is 
mapped to the RequestURIModule in cocoon.xconf :

<component-instance logger="core.modules.input" name="requestURI"


<component-instance logger="core.modules.input" name="request"

It doesn't matter what name you give it, as long as you use the 
same in both sitemap and cocoon.xconf.

The second part, always 'requestURI', is handled internally by 
org.apache.cocoon.components.modules.input.RequestURIModule. This
handling currently returns the URI as discussed and does not 
change based on the mapped name of the module.

-----Original Message-----
From: Sonny Sukumar []
Sent: Thursday, October 09, 2003 2:21 PM
Subject: request:requestURI vs requestURI:requestURI

Hey guys,

Does anybody know the difference between {request:requestURI} and 
{requestURI:requestURI}?  I was discussing these things with Tony and Peter 
on the list yesterday, but I didn't get this quite clear in my mind.

Do either of these return the full query string as well?  I think I need 

FYI, the "requestURI" refers is not declared in cocoon.xconf by default 
(apparently) and refers to this class:



Add MSN 8 Internet Software to your existing Internet access and enjoy 
patented spam protection and more.  Sign up now!

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message