cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <>
Subject Re: [RT] A Unified Environment Model?
Date Thu, 03 Mar 2005 14:56:43 GMT
Sylvain Wallez wrote:

> Daniel Fagerstrom wrote:
>> Vadim Gritsenko wrote:
>>> Daniel Fagerstrom wrote:
>>>> The important thing for the "modules" is to provide script friendly 
>>>> access of environment data in a simple way. I assumed that the 
>>>> easiest way would be to support "POJO" interfaces with get and set 
>>>> methods and Maps so that it would be easy to use for the reflection 
>>>> parts of ELs and scripting languages, but I don't know that much 
>>>> about it.
>>> You may want to look at:

>>> Basically, what they did, they abstracted out servlet API:
>>>   request.getParameter()
>>>   request.getAttribute()
>>>   request.getSession().getAttribute()
>>>   ...
>>> Into POJO / Maps, EL friendly interface:
>>>   context.getRequestParameterMap()
>>>   context.getRequestMap()
>>>   context.getSessionMap()
>>>   context.getApplicationMap()
>>> Having something like that (parameters/attributes access via maps) 
>>> in Cocoon environment probably is not a bad idea.
>> You mean that we should add such methods in 
>> o.a.c.environment.Request, Session etc? Yes, that seem to be a good 
>> idea, then we don't need any Servlet API specific code for the script 
>> friendly embeding.
> Note that we already have no servlet-api specific code as the 
> environment is abstracted in Cocoon. ExternalContext can be considered 
> as the JSF equivalent of our object model. 

I know, I expressed my self in a sloopy way. What I meant is that our 
environment abstraction is very close to the servlet API, but we could 
add some methods like the one Vadim suggests to make our environment 
more POJO styled, and as a consequence more EL friendly.


View raw message