Resource and String location parameters.
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 a suggestion for bean definition readers that want to follow standard naming conventions.
org.springframework.core.io.Resource
| Modifier and Type | Method and Description |
|---|---|
| public ClassLoader | |
| public BeanNameGenerator | getBeanNameGenerator()
Return the |
| public BeanDefinitionRegistry | |
| public ResourceLoader | |
| public int | Returns: the number of bean definitions foundthe resource descriptor resource)Load bean definitions from the specified resource. |
| public int | Returns: the number of bean definitions foundthe resource descriptors resources)Load bean definitions from the specified resources. |
| public int | Returns: the number of bean definitions foundthe resource location, to be loaded with the location)ResourceLoader
(or ResourcePatternResolver) of this bean definition readerLoad bean definitions from the specified resource location. |
| public int | Returns: the number of bean definitions foundthe resource locations, to be loaded with the locations)ResourceLoader
(or ResourcePatternResolver) of this bean definition readerLoad bean definitions from the specified resource locations. |
| getBeanClassLoader | back to summary |
|---|---|
| public ClassLoader getBeanClassLoader() Return the class loader to use for bean classes.
| |
| getBeanNameGenerator | back to summary |
|---|---|
| public BeanNameGenerator getBeanNameGenerator() Return the | |
| getRegistry | back to summary |
|---|---|
| public BeanDefinitionRegistry getRegistry() Return the bean factory to register the bean definitions with. The factory is exposed through the | |
| getResourceLoader | back to summary |
|---|---|
| public ResourceLoader getResourceLoader() Return the Can be checked for the A 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 path based resource loading. There is also a
| |
| loadBeanDefinitions | back to summary |
|---|---|
| public int loadBeanDefinitions(Resource resource) throws BeanDefinitionStoreException Load bean definitions from the specified resource.
| |
| loadBeanDefinitions | back to summary |
|---|---|
| public int loadBeanDefinitions(Resource... resources) throws BeanDefinitionStoreException Load bean definitions from the specified resources.
| |
| loadBeanDefinitions | back to summary |
|---|---|
| public int loadBeanDefinitions(String location) throws BeanDefinitionStoreException Load bean definitions from the specified resource location. The location can also be a location pattern, provided that the
| |
| loadBeanDefinitions | back to summary |
|---|---|
| public int loadBeanDefinitions(String... locations) throws BeanDefinitionStoreException Load bean definitions from the specified resource locations.
| |