On Thu, May 21, 2009 at 6:04 AM, ant elder <[email protected]> wrote: > Having a way to define "default" impls and have those easily overriden > would be really useful. We've often needed to be able to do that and > have clunky work arounds at various places to deal with not having any > defaulting mechanism. But there are several other problems with the > current discovery mechanism which it would be good to fix, some of > them have already been mentioned in this thread, here's the list i can > think of: > > 1) unable to define default impls and have an easy way to override the default > 2) random startup order so intermittent fails when a service looks up > another service during startup > 4) how to choose when there are multiple impls > 5) choose impls programaticaly at runtime so impls can enable/disable > themselves based on the environment > > Before suggesting approaches on how to fix do we agree with that list > of things to fix? > > ...ant >
I think 1 and 4 (what was 3?) are the same issue. Not sure about 5. Sounds like a solution. I would prioritize as follows because 2 keeps hurting us. 2) random startup order so intermittent fails when a service looks up another service during startup 1) unable to define default impls and have an easy way to override the default Simon
