On Mon, 25 Nov 2002 23:53, Berin Loritsch wrote: > > Using the "Services JAR specification" is really misusing it > > as it is meant to > > be a way to map implementations for services. > > And that is what I was intending. > > I.e. I have a new service (component): > > org.dhaven.myexample.Echo > > In my JAR I have three implementations, but in another JAR I might have > another three. Using the Services JAR specification, I can > detect all my possibilities for my system.
That would be fine if each component only implemented one service. However each component can implement multiple services. Much better to just have a registry of components and then lookup metadata for the component. -- Cheers, Peter Donald *-----------------------------------------------------* | Never argue with an idiot, they'll drag you down to | | their level, and beat you with experience | *-----------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
