The idea is that one subclass can use the {@link InstallerLookup} design tolookup installers for components (and hence create the components themselves), whereas another subclass might simply use Spring (or another DI container) to inject in the components according to some Spring-configured application context.
|
|
|
|