cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: [RT] Environment Revamping
Date Fri, 19 Oct 2001 13:05:56 GMT
Martin Man wrote:
> 
> On Fri, Oct 19, 2001 at 12:08:15PM +0200, Sylvain Wallez wrote:
> >
> > Extending Map is a good idea : only the parameter type will change, so
> > this will require only a recompilation without code change (provided
> > that we route get(RESPONSE_OBJECT) to getResponse(), etc). But this also
> > clearly states that data can be added to the object model using put().
> > There has been several posts in the past giving me the impression this
> > was possible, but not encouraged. Was this impression wrong ?
> 
> no you're sure the discussion was about using the objectModel as a generic
> communication space for component exchange between different pipeline
> components, eg. generator (or action) placing something to the objectModel and
> transformer taking it out, ....
> 
> but if I recall correctly giacomo (and I agree) stated that this should not be
> used at all and proposed to meke the objectModel readOnly to avoid confusion,
> becuase there are already objects like session and request that are suited for
> this type of communication
> 
> so my 0.2 cents are to make new RequestContext readOnly for adding new objects
> to it and provide some set/getAttribute methods which will wrap the existing
> set/getAttribute methods for different underlying contexts...

In that case, RequestContext should extend Avalon Context, which only exposes
the get() method.  Any well behaved component will survive with only a recompile
necessary.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message