> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: den 18 februari 2002 20:48
> To: Avalon Developers List
> Subject: Re: [VOTE] RE: ComponentManager interface
>
>
> On Tue, 19 Feb 2002 00:45, Leo Sutic wrote:
> > > From: Peter Donald [mailto:[EMAIL PROTECTED]]
> > >
> > > On Tue, 19 Feb 2002 00:06, Leo Sutic wrote:
> > > > > From: Peter Donald [mailto:[EMAIL PROTECTED]]
> > > > >
> > > > > different scope of resource allocation is treated as different
> > > > > scopes?
> > > >
> > > > But these scopes coexist in the same component, and you assume that
> > > > there are only two - request and static.
> > >
> > > do i ? Have a look at the javadoc at
> > >
> /jakarta-avalon/src/java/org/apache/avalon/framework/context/Context.java
> >
> > 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?
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
