Folks
I would like to add these two new framework interfaces (see below). I
would use them in EOB, with the understanding that they will/might
dissapear one day.
+ 1 from me for adding to jakarta-avalon
Incidentally, I see the future like this:
1) Interfaces get added
2) Berin, Peter et al consider "Component" marker interface as
unecessary in the same way as "Service" was unecessary
3a) Framework 5.0 Composable given same method signatures as
Composable2, Likewise ComponentManager for CompMgr2.
3b) Composable2 has methods removed, extends Composable and is marked as
deprecated.
4) Framework 5.x Composable2 etc removed.
Regards,
- Paul H
> Berin,
>
>>> As to the Component interface, it is currently used in the
>>> ComponentManager
>>> API, and is rather central to the way things work. We _can't_
>>> change that
>>> in Avalon 4.x. When we get to the point where we want to aim for
>>> 5.0, we
>>> will revisit the whole concept of marker interfaces.
>>
>>
>>
>> I know dude. With EOB I was going to use all the Framework
>> interfaces but decided I could not use Composable because it have
>> back a Component. EOB beans getting interfaces from anywhere, remote
>> or local, to force these to impl Component was impossible.
>>
>> I am happy to wait until 5.0, however changing a return value (on
>> lookup()) from Component to Object has far fewer implications than
>> the other way around....
>
>
> Is there any chance we could add.....
>
> interface Composable2 {
> void compose(ComponentManager2 compMgr) throws ComponentException;
> }
>
> interface ComponentManager2 {
> Object lookup(String s) throws ComponentException;
> }
>
> ... in advance of this 5.0 migration? I'd like to be an early user....
>
> - Paul
>
>
>
> --
> 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]>
