org.springframework.context.annotation Documentation Differences

This file contains all the changes in documentation in the package org.springframework.context.annotation as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Beans on which the current bean depends. Any beans specified are guaranteed to be created by the container before this bean. Used infrequently in cases where a bean does not explicitly depend on another through properties or constructor arguments, but rather depends on the side effects of another bean's initialization. Note: This attribute will not be inherited by child bean definitions, hence it needs to be specified per concrete bean definition.

May be used on any class directly or indirectly annotated with org.springframework.stereotype.Component or on methods annotated with Bean.

Using DependsOn at the class level has no effect unless component-scanning is being used. If a DependsOn-annotated class is declared via XML, DependsOn annotation metadata is ignored, and {@code } is respected instead. @author Juergen Hoeller @since 3.0

Interface to be implemented by types that register additional bean definitions when processing @Configuration classes. Useful when operating at the bean definition level (as opposed to {@code @Bean} method/instance level) is desired or necessary.

Along with {@code @Configuration} and ImportSelector, classes of this type may be provided to the @Import annotation (or may also be returned from an {@code ImportSelector}).

An ImportBeanDefinitionRegistrar may implement any of the following Aware interfaces, and their respective methods will be called prior to .registerBeanDefinitions:

• BeanFactoryAware
• BeanClassLoaderAware
• ResourceLoaderAware

See implementations and associated unit tests for usage examples. @author Chris Beams @since 3.1 @see Import @see ImportSelector @see Configuration