cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <jer...@media.demon.co.uk>
Subject Re: FOM, views, and input modules
Date Tue, 24 Jun 2003 09:13:58 GMT

On Monday, June 23, 2003, at 04:57 AM, Christopher Oliver wrote:

> I modified the FOM implementation in the scratchpad to make the FOM 
> available to the view layer, thinking that the view author also should 
> see the FOM (See FOM_JavaScriptFlowHelper.java), rather than the raw 
> Request, Response, etc. Do others agree with this?
>
> I also modified the GarbageGenerator to use the FOM.
>
> So because of the FOM you can't do this in a flow script anymore:
>
>   cocoon.request.sitemapURI
>
> likewise in a Garbage view template you can no longer do this:
>
>    <page whatever="{$request/sitemapURI}">
>
> in both cases because the FOM doesn't expose the "sitemapURI" property 
> of the Request.
>
> However the input modules give full access to the original Java 
> Request object, so in the sitemap you can still do this:
>
>    <map:call function="whatever">
>        <map:parameter name="whatever" value="{request:sitemapURI}"/>
>
> and pass it as a parameter to your flowscript, bypassing the FOM (!)
>
> This seems inconsistent to me. What do others think?

I like to have access to the URI of the request from within the 
flowscript.
Specially because I put my Continuation in a request param and match it 
with the RequestParam Matcher (I hate seeing that in the URL).
So passing the URI from the sitemap is not so easy in my case ....

regards Jeremy


Mime
View raw message