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 14:57:55 GMT
 
Sylvain Wallez wrote:
> 
> >We already have cocoon.context, couldn't we make things 
> available from there?
> >  
> >
> 
> Mmmh... don't know if it's a good idea, as the Cocoon core 
> currently doesn't rely on custom attributes in the 
> environment objects (unless I'm mistaken). This would 
> complexify things a bit, IMO.
> 
Hmm, ok we currently have a o.a.c.environment.Context which
has some functions from the servlet context object and attributes.
Currently these attributes are not really used.

And we have o.a.a.context.Context which is a map containing
many important information about the application.

For me it seems that two contexts is one too much :)
So, why not combining those somehow. Currently you get the
o.a.c.e.Context from the avalon context.

Now, we could for example store all information we currently
have in the avalon context into the environment context
and using the environment context as the only reference
for application information. If you need this context
you can get it from the avalon context. The avalon context
only contains this single piece of information (of course
for compatibility we let everything remain there as 
well).
Then in flow, cocoon.context works perfect.

WDYT?

Carsten


Mime
View raw message