Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 25391 invoked by uid 500); 19 Oct 2001 10:57:23 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 25362 invoked from network); 19 Oct 2001 10:57:23 -0000 Date: Fri, 19 Oct 2001 12:55:43 +0200 From: Martin Man To: cocoon-dev@xml.apache.org Subject: Re: [RT] Environment Revamping Message-ID: <20011019125543.A26543@renie.dyndns.org> Mail-Followup-To: cocoon-dev@xml.apache.org References: <3BCEF816.E59ED219@apache.org> <3BCFFB8F.44C3C842@anyware-tech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <3BCFFB8F.44C3C842@anyware-tech.com> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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... > > Sylvain. > -- > Sylvain Wallez > Anyware Technologies - http://www.anyware-tech.com martin -- 2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223 --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org