> I'd be quite sad to have to abandon DependencyManager for this reason.. > Does anyone know of a workaround, or a future release that would address > this issue?
I had some time yesterday evening so I added support for supplying your own "default implementation" for a service dependency. If you do so, it will be used instead of the null object. The new method (on a ServiceDependency) is called setDefaultImplemenation(Object) and the argument can be either of type class (which will lazily be instantiated by invoking the default constructor) or an instance you already created. I did not yet test this feature, but feel free to check out the latest version and build and test it. Greetings, Marcel
