All Known Implementing Classes:
XmlBeanDefinitionReader, PropertiesBeanDefinitionReader, AbstractBeanDefinitionReader
Concrete bean definition readers can of course add additional load and register methods for bean definitions, specific to their bean definition format.
Note that a bean definition reader does not have to implement this interface. It only serves as suggestion for bean definition readers that want to follow standard naming conventions.
Juergen - Hoeller1.1 - | Method from org.springframework.beans.factory.support.BeanDefinitionReader Summary: |
|---|
| getBeanClassLoader, getBeanFactory, getBeanNameGenerator, getRegistry, getResourceLoader, loadBeanDefinitions, loadBeanDefinitions, loadBeanDefinitions, loadBeanDefinitions |
| Method from org.springframework.beans.factory.support.BeanDefinitionReader Detail: |
|---|
|
The factory is exposed through the BeanDefinitionRegistry interface, encapsulating the methods that are relevant for bean definition handling. |
|
The factory is exposed through the BeanDefinitionRegistry interface, encapsulating the methods that are relevant for bean definition handling. |
Null suggests that absolute resource loading is not available for this bean definition reader. This is mainly meant to be used for importing further resources from within a bean definition resource, for example via the "import" tag in XML bean definitions. It is recommended, however, to apply such imports relative to the defining resource; only explicit full resource locations will trigger absolute resource loading. There is also a |
|
|
The location can also be a location pattern, provided that the ResourceLoader of this bean definition reader is a ResourcePatternResolver. |
|