cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: FOM & input modules
Date Wed, 26 Jan 2005 13:39:45 GMT
Sylvain Wallez wrote:
> Carsten Ziegeler wrote:
> 
>> Hmm, the question is: how can a pluggable object model work - or how 
>> can it be extended? What about using...input modules for exactly this? 
>> We create a way of "mounting" input modules into the object model, 
>> like this:
>> <object-model>
>>   <mount input-module="skin" path="cocoon.skin"/>
>> </object-model>
>>
>> And then you can simple access the info by ${cocoon.skin.something}.
> 
> 
> I like it. Object model and input modules are just different names for 
> similar things: accessing environmental data. Also, it's better to 
> attach IMs to the cocoon object rather than as root variables, as it 
> avoids name clashes with template variables.
> 
> Something we have to be careful of, though, is that properties of the 
> cocoon object comes both from the OM (request, response, context) and 
> modules, and that it should be forbidden to have IMs having the same 
> name as OM keys.

... unless cocoon.request, response, context are implemented as corresponding 
input modules ... then everything under "cocoon." becomes an input module ;-)

Vadim

Mime
View raw message