> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: den 18 februari 2002 21:02
> To: Avalon Developers List
> Subject: Re: [VOTE] RE: ComponentManager interface
>
>
> On Tue, 19 Feb 2002 07:07, Leo Sutic wrote:
> > > > So your proposal is basically that we do away with the
> > > > Contextualizable, Composable interfaces and pass the CM in a Context
> > > > object for each call to a component?
> > >
> > > eh?
> >
> > That was my reaction, too.
> >
> > If you have (as in the javadoc):
> >
> > void doMagic( int param1, int param2, Context otherParamsInHere );
> >
> > Then the CM goes in the Context, right? You pass the per-request CM
> > in the Context, right?
> >
> > Now, if a Context is passed in to every method, and if a CM is passed
> > in that context, and it is assumed that the context and the CM passed
> > in are to be used in that method, then what need is there for Composable
> > and Contextualizable?
>
> for static access?
But then you can not have poolable components in static access, as the CM
will not let you release them. Unless you want the called component to
lookup some components from one CM, some from another and some from a third.
And how do you resolve the issue that the caller now is responsible for providing
all required components to the component being called?
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
