@NonNullApi @NonNullFields
See: Description
| Interface | Description | 
|---|---|
| TargetSourceCreator | Implementations can create special target sources, such as pooling target
 sources, for particular beans. | 
| Class | Description | 
|---|---|
| AbstractAdvisorAutoProxyCreator | Generic auto proxy creator that builds AOP proxies for specific beans
 based on detected Advisors for each bean. | 
| AbstractAutoProxyCreator | BeanPostProcessorimplementation
 that wraps each eligible bean with an AOP proxy, delegating to specified interceptors
 before invoking the bean itself. | 
| AbstractBeanFactoryAwareAdvisingPostProcessor | Extension of  AbstractAutoProxyCreatorwhich implementsBeanFactoryAware,
 adds exposure of the original target class for each proxied bean
 (AutoProxyUtils.ORIGINAL_TARGET_CLASS_ATTRIBUTE),
 and participates in an externally enforced target-class mode for any given bean
 (AutoProxyUtils.PRESERVE_TARGET_CLASS_ATTRIBUTE). | 
| AutoProxyUtils | Utilities for auto-proxy aware components. | 
| BeanFactoryAdvisorRetrievalHelper | Helper for retrieving standard Spring Advisors from a BeanFactory,
 for use with auto-proxying. | 
| BeanNameAutoProxyCreator | Auto proxy creator that identifies beans to proxy via a list of names. | 
| DefaultAdvisorAutoProxyCreator | BeanPostProcessorimplementation that creates AOP proxies based on all
 candidateAdvisors in the currentBeanFactory. | 
| InfrastructureAdvisorAutoProxyCreator | Auto-proxy creator that considers infrastructure Advisor beans only,
 ignoring any application-defined Advisors. | 
| ProxyCreationContext | Holder for the current proxy creation context, as exposed by auto-proxy creators
 such as  AbstractAdvisorAutoProxyCreator. | 
The various post-processors in this package need only be added to an ApplicationContext (typically in an XML bean definition document) to automatically proxy selected beans.
NB: Automatic auto-proxying is not supported for BeanFactory implementations, as post-processors beans are only automatically detected in application contexts. Post-processors can be explicitly registered on a ConfigurableBeanFactory instead.