for Spring AOP? Mixing aspect types Proxying mechanisms Understanding AOP proxies Programmatic creation of @AspectJ Proxies Using AspectJ with Spring applications Using AspectJ to dependency inject domain (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet container. The Context module also supports Java EE features meta-annotations to create custom composed annotations and reduce configuration duplication across a test suite. Active bean definition profiles can now be resolved programmatically, simply by implementing a custom

for Spring AOP? Mixing aspect types Proxying mechanisms Understanding AOP proxies Programmatic creation of @AspectJ Proxies Using AspectJ with Spring applications Using AspectJ to dependency inject domain (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet container. The Context module also supports Java EE features meta-annotations to create custom composed annotations and reduce configuration duplication across a test suite. Active bean definition profiles can now be resolved programmatically, simply by implementing a custom

....................................................................... 250 11.7. Programmatic creation of @AspectJ Proxies ................................................... 253 11.8. Using AspectJ (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet container. The Context module also supports Java EE features meta-annotations to create custom composed annotations and reduce configuration duplication across a test suite. • Active bean definition profiles can now be resolved programmatically, simply by implementing a

....................................................................... 243 11.7. Programmatic creation of @AspectJ Proxies ................................................... 246 11.8. Using AspectJ (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet container. The Context module also supports Java EE features meta-annotations to create custom composed annotations and reduce configuration duplication across a test suite. • Active bean definition profiles can now be resolved programmatically, simply by implementing a

exception handling for clearer wrapping of nested exceptions * DefaultListableBeanFactory performs bean creation within a PrivilegedAction (for SecurityManager compatibility) * optimized DefaultListableBeanFactory's expose an "order" bean property * "depends-on" kicks in before the affected bean is entering its creation phase; can be used to resolve circular refs * added "registers-scope" annotation to spring-tool -------- General * updated build to use JUnit 4.4 for the tiger test suite while sticking with JUnit 3.8 for the main test suite * moved GlassFish and OC4J instrumentation support from spring-context-support

exception handling for clearer wrapping of nested exceptions * DefaultListableBeanFactory performs bean creation within a PrivilegedAction (for SecurityManager compatibility) * optimized DefaultListableBeanFactory's expose an "order" bean property * "depends-on" kicks in before the affected bean is entering its creation phase; can be used to resolve circular refs * added "registers-scope" annotation to spring-tool -------- General * updated build to use JUnit 4.4 for the tiger test suite while sticking with JUnit 3.8 for the main test suite * moved GlassFish and OC4J instrumentation support from spring-context-support

* fixed AbstractAutowireCapableBeanFactory's "configureBean" (@Configurable) to avoid bean name creation for inner beans * fixed AbstractAutowireCapableBeanFactory to skip invocation of Instantiation Lifecycle interface * AbstractApplicationContext processes Lifecycle callbacks in the order of bean creation by default * AbstractApplicationContext explicitly freezes its bean factory configuration at the exception handling for clearer wrapping of nested exceptions * DefaultListableBeanFactory performs bean creation within a PrivilegedAction (for SecurityManager compatibility) * optimized DefaultListableBeanFactory's

singleton exposure to remove singleton factory after creation of singleton object * DefaultSingletonBeanRegistry only exposes related causes on outermost creation exception (avoiding excessive logging) * Def DefaultListableBeanFactory passes full inherited AccessControlContext to the AccessController for bean creation * DefaultListableBeanFactory does not eagerly initialize target beans when autowiring a PriorityOrdered * fixed AbstractAutowireCapableBeanFactory's "configureBean" (@Configurable) to avoid bean name creation for inner beans * fixed AbstractAutowireCapableBeanFactory to skip invocation of Instantiatio

DefaultListableBeanFactory passes full inherited AccessControlContext to the AccessController for bean creation * DefaultListableBeanFactory does not eagerly initialize target beans when autowiring a PriorityOrdered * fixed AbstractAutowireCapableBeanFactory's "configureBean" (@Configurable) to avoid bean name creation for inner beans * fixed AbstractAutowireCapableBeanFactory to skip invocation of Instantiation Lifecycle interface * AbstractApplicationContext processes Lifecycle callbacks in the order of bean creation by default * AbstractApplicationContext explicitly freezes its bean factory configuration at the

DefaultListableBeanFactory passes full inherited AccessControlContext to the AccessController for bean creation * DefaultListableBeanFactory does not eagerly initialize target beans when autowiring a PriorityOrdered * fixed AbstractAutowireCapableBeanFactory's "configureBean" (@Configurable) to avoid bean name creation for inner beans * fixed AbstractAutowireCapableBeanFactory to skip invocation of Instantiation Lifecycle interface * AbstractApplicationContext processes Lifecycle callbacks in the order of bean creation by default * AbstractApplicationContext explicitly freezes its bean factory configuration at the