avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: Service Interface
Date Sun, 03 Feb 2002 00:40:05 GMT

>> 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:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message