Proposal:
(a) mark the lookup operation as deprecated
(b) add a new method "resolve" that is
functionally equivalent to "lookup" but returns
Object instead of Component
(c) change the argument type on the release from
Component to Object.
Steve.
> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, 09 February, 2002 09:06
> To: Avalon Developers List
> Subject: Re: ComponentManager interface
>
>
> On Sat, 9 Feb 2002 11:53, Stephen McConnell wrote:
> > Given that Component's existence is under considered of being
> > depreciated, can anyone provide some hints as to probability
> > and timeframe of the ComponentManager.lookup operation returning
> > Object instead of Component. The reason I'm asking is that such
> > a change would be very beneficial to the things I'm working on
> > that do not and will never implement Component
> > (e.g. org.omg.CORBA.Object).
>
> Im in a similar position in a couple of projects where I ended up
> creating
> another siilar interface. So I guess that makes 3 committers who would
> benefit from something like this. However we can't afford to
> break anything
> in Cocoon land. So maybe we just create something that is a stop-gap till
> Framework 5.0 ?
>
> --
> Cheers,
>
> Pete
>
> --------------------------------------------------
> you've made a dangerous leap right over common
> sense, like some kind of metaphysical Evil Knievel
> --------------------------------------------------
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
