Hamilton Verissimo de Oliveira wrote: > > -----Mensagem original----- > De: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > > > So, I think it is much easier to write: > > lookup(GreatComponent.class) for the first case and > > lookup(GreatComponent.class, key) for the second one. > > I don't think this cover all possible situations. Please take > a look at > > http://www.javaworld.com/javaworld/jw-02-2000/jw-02-jiniology.html > > I've liked the ServiceTemplate idea for long time. This plus > a pluggable discovery strategy will cover all possible > situations. Or not. :-) > Ok, this covers a lot of situations and imho too many :) I like it "simple". Perhaps my view of a lookup is too simple but I currently have two use cases: a) I want a component that provides service XY b) I want a specific (named) component that provides service XY The service is defined by a (Java) interface - so I think my use cases are covered with my simpler approach :)
Can you give some use cases or scenarios where you need your version of a discovery strategy? Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
