You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the latest snapshot of Spring change the way it gets Bean in DefaultLifecycleProcessor.
In 3.0.rc3, all FactoryBean itself which implements SmartLifecycle will get auto-started. However, the FactoryBean itself is not started by Spring in the latest snapshot.
Fixed for 3.0 GA through a refined lookup of both SmartLifecycle beans and already initialized Lifecycle singletons (which includes FactoryBean instances).
Would be great if you could give the latest snapshot a try tomorrow...
Liu, Yinwei David opened SPR-6545 and commented
It looks like the latest snapshot of Spring change the way it gets Bean in DefaultLifecycleProcessor.
In 3.0.rc3, all FactoryBean itself which implements SmartLifecycle will get auto-started. However, the FactoryBean itself is not started by Spring in the latest snapshot.
Affects: 3.0 RC3
Issue Links:
Referenced from: commits 9d2f793, 42c7be4, a0c4d2c
The text was updated successfully, but these errors were encountered: