InitializingBean negate lazy-init="true" ?
I've noticed that a bean configured with lazy-init="true" is always being loaded, even if it's not referenced by any other bean.
The bean in question extends SqlMapClientDaoSupport which implements InitializingBean...is the fact that it implements this interface causing it to ignore the lazy initialization?
Is there any other way around this? We have properties that determine what beans to load. Loading this bean typically causes errors so at the moment we are just removing it from the configuration, which is not very seamless.