cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [VOTE] Unrestricting the FOM
Date Tue, 15 Jun 2004 17:07:19 GMT
Sylvain Wallez wrote: 
> 
> Makes sense. And migrating some stuff to the env-context may 
> help removing some dependencies on Avalon. But whe have to be 
> very careful about what attributes we want to move from 
> avalon-context to env-context, and be sure they will still 
> make sense in a new container and within blocks.
> 
Yepp.

> 
> The only point I'm not sure about is the object model: should 
> it be in the env-context, since it also contains that 
> env-context? Kind of circular dependency that may be confusing...
> 
Yepp, that's true. I would say we leave this in the avalon
context then.

> What we need actually is some kind of mini-environment that 
> would give access only to the "safe" properties of 
> o.a.c.e.Environment, i.e. mainly the object model and 
> attributes, plus access to the current avalon-context 
> attributes through type-safe getter methods.
> 
> >Then in flow, cocoon.context works perfect.
> >  
> >
> 
> Yupp. <rt>And with an IOC type2/3 container we could even 
> totally remove the dependency on avalon-context by simply have a
> setContext(o.a.c.e.Context) method ;-)</rt>
> 
Yepp :), it would work today if we would move to Fortress.....

Carsten


Mime
View raw message