All Known Implementing Classes:
DefaultListableBeanFactory, FactoryBeanRegistrySupport, AbstractAutowireCapableBeanFactory, ConfigurableBeanFactory, AbstractBeanFactory, DefaultSingletonBeanRegistry, XmlBeanFactory, ConfigurableListableBeanFactory
The ConfigurableBeanFactory interface extends this interface.
Juergen - Hoeller2.0 - | Method from org.springframework.beans.factory.config.SingletonBeanRegistry Summary: |
|---|
| containsSingleton, getSingleton, getSingletonCount, getSingletonNames, registerSingleton |
| Method from org.springframework.beans.factory.config.SingletonBeanRegistry Detail: |
|---|
Only checks already instantiated singletons; does not return The main purpose of this method is to check manually registered singletons (see #registerSingleton ). Can also be used to check whether a singleton defined by a bean definition has already been created. To check whether a bean factory contains a bean definition with a given name,
use ListableBeanFactory's Use BeanFactory's |
Only checks already instantiated singletons; does not return an Object for singleton bean definitions which have not been instantiated yet. The main purpose of this method is to access manually registered singletons (see #registerSingleton ). Can also be used to access a singleton defined by a bean definition that already been created, in a raw fashion. |
Only checks already instantiated singletons; does not count singleton bean definitions which have not been instantiated yet. The main purpose of this method is to check manually registered singletons (see #registerSingleton ). Can also be used to count the number of singletons defined by a bean definition that have already been created. |
Only checks already instantiated singletons; does not return names for singleton bean definitions which have not been instantiated yet. The main purpose of this method is to check manually registered singletons (see #registerSingleton ). Can also be used to check which singletons defined by a bean definition have already been created. |
The given instance is supposed to be fully initialized; the registry
will not perform any initialization callbacks (in particular, it won't
call InitializingBean's If running within a full BeanFactory: Register a bean definition instead of an existing instance if your bean is supposed to receive initialization and/or destruction callbacks. Typically invoked during registry configuration, but can also be used for runtime registration of singletons. As a consequence, a registry implementation should synchronize singleton access; it will have to do this anyway if it supports a BeanFactory's lazy initialization of singletons. |