Nice to see some good discussion happening about this. I'm going to try to split this out into another threads.
As for discovery methods: On Mon, 2003-09-01 at 02:54, Stephen McConnell wrote: > > Frankly I don't think the current ServiceManager interface is a good > candidate for dynamic service discovery. It does not provide support for > the supply of a selection policy and its exception suite needs to be > beefed up a lot. > Not the current ServiceManager interface, no. My point was, given the two roles of the ServiceManager (dependency, discovery), I tended to use it more for discovery. The ServiceLocator example you gave was along the lines of what I was thinking. Another option is to first get jndi exporting of services and then do all service discovery via the jndi bindings. The discovery service itself could then also be a JNDI Context or at least provide one. Then you get both JNDI exporting and internal service discovery. Any downsides to that? Speaking of Contexts, what about the Avalon Context? Is it providing dependencies or is it a discovery service? I like what Merlin now allows us to do in the Context, but I think it's always been confusing have two lookup objects (Context and ServiceManager). Currently I tend to think of the Context as a Container wide configuration object. -- jaaron <http://jadetower.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
