org.springframework.beans.factory.support Documentation Differences

This file contains all the changes in documentation in the package org.springframework.beans.factory.support 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.

Abstract bean factory superclass that implements default bean creation, with the full capabilities specified by the RootBeanDefinition class. Implements the org.springframework.beans.factory.config.AutowireCapableBeanFactory interface in addition to AbstractBeanFactory's .createBean method.

Provides bean creation (with constructor resolution), property population, wiring (including autowiring), and initialization. Handles runtime bean references, resolves managed collections, calls initialization methods, etc. Supports autowiring constructors, properties by name, and properties by type.

The main template method to be implemented by subclasses is .resolveDependency(DependencyDescriptor, String, Set, TypeConverter), used for autowiring by type. In case of a factory which is capable of searching its bean definitions, matching beans will typically be implemented through such a search. For other factory styles, simplified matching algorithms can be implemented.

Note that this class does not assume or implement bean definition registry capabilities. See DefaultListableBeanFactory for an implementation of the org.springframework.beans.factory.ListableBeanFactory and BeanDefinitionRegistry interfaces, which represent the API and SPI view of such a factory, respectively. @author Rod Johnson @author Juergen Hoeller @author Rob Harrop @author Mark Fisher @author Costin Leau @author Chris Beams @author Sam Brannen @since 13.02.2004 @see RootBeanDefinition @see DefaultListableBeanFactory @see BeanDefinitionRegistry

Extract a filtered set of PropertyDescriptors from the given BeanWrapper, excluding ignored dependency types or properties defined on ignored ignored dependency interfaces. @param bw the BeanWrapper the bean was created with @return the filtered PropertyDescriptors @see #isExcludedFromDependencyCheck

Create a new AbstractBeanDefinition as a deep copy of the given bean definition. @param original the original bean definition to copy from @deprecated since Spring 2.5, in favor of .AbstractBeanDefinition(BeanDefinition)

Create a new AbstractBeanDefinition as a deep copy of the given bean definition. @param original the original bean definition to copy from

Override settings in this bean definition (assumablypresumably a copied parent from a parent-child inheritance relationship) from the given bean definition (assumablypresumably the child). @deprecated since Spring 2.5, in favor of .overrideFrom(BeanDefinition)

Override settings in this bean definition (assumablypresumably a copied parent from a parent-child inheritance relationship) from the given bean definition (assumablypresumably the child).

• Will override beanClass if specified in the given bean definition.
• Will always take abstract, scope, lazyInit, autowireMode, dependencyCheck, and dependsOn from the given bean definition.
• Will add constructorArgumentValues, propertyValues, methodOverrides from the given bean definition to existing ones.
• Will override factoryBeanName, factoryMethodName, initMethodName, and destroyMethodName if specified in the given bean definition.

Constant that indicates the container should attempt to infer the destroy method name for a bean as opposed to explicit specification of a method name. The value {@value} is specifically designed to include characters otherwise illegal in a method name, ensuring no possibility of collisions with a legitimately named methods having the same name.

Default object instantiation strategy for use in BeanFactories. Uses CGLIB to generate subclasses dynamically if methods need to be overridden by the container, to implement Method Injection. Using Method Injection features requires CGLIB on the classpath. However, the core IoC container will still run without CGLIB being available. @author Rod Johnson @author Juergen Hoeller @since 1.1