Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [RT] Access to the object model
Date: Mon, 19 May 2003 15:15:23 +0200
Message-ID: <LKENJPKDAIKAPKHEOCMMIEDEDKAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <487FF56C-89FA-11D7-A398-000393B61B56@apache.org>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"


Peter Royal wrote:
> 
> On Monday, May 19, 2003, at 06:14  AM, Carsten Ziegeler wrote:
> > c) Use the Contextualizable interface and put a "handler" in
> >    the context object.
> >
> > Now, the most simple approach is a), but that'S not IoC. - I
> > think the cleanest solution is b), but that would require
> > a new marker interface.
> >
> > I currently tend to a),
> >
> > What do you think? Is is bad to get the object model in
> > a custom component?
> 
> I'd say (c).
> 
> You could do a straight dump of the object model into a Context..
> 
> final DefaultContext objectModelContext = new DefaultContext( 
> objectModel, parentContext );
> 
> ContainerUtil.contextualize( objectModelContext, component );
> 
> ....
> 
> Components then just do:
> 
> Request req = (Request) context.get( "request" );
> 
I'm not sure if this is working. A component can be thread safe,
but each request has an own object model, so I think at least the context
must either be thread local (which would not be that efficient) or
you must store some kind of thread handler for the object model
in the context. Or do I oversee something?

Carsten