So there is a catch (22). Didn't think about that! And it's a very good reason not to provide a ServiceInjector service. The logic could still be encapsulated in a class and be reused as such. Even as a convenience method as Marcus suggests.
--knut On Wed, 27 Oct 2004 11:14:44 -0400, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Don't forget the bootstrap issues; the BuilderFactory can't construct > itself! So it may have a captive instance of ServiceInjectorImpl that > would be different from the one accessed (via the normal paths) by > other services. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
