It appears as if Spring instantiates a class when a configuration file is loaded instead of deferring to first use of that bean, regardless of whether the lazy-init parameter has been set to true. It throws a "ClassNotFoundException".
Is there any way to defer the instantiation of the class until first use?
We are attempting to use Spring as sort of a pseudo-registry. We'd like to be able to deploy a Spring ApplicationContext xml file which has definitions for all of our Services, but allow users to only load in the particular services they need.


Reply With Quote