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

locally (avoiding eager init) * PropertyPathFactoryBean logs a warning if the target bean is still in creation at the time of obtaining the property * exposed public "copyRegisteredEditorsTo" method on ConfigurableBeanFactory descriptive exception if incompatible * Portlet AbstractCommandController falls back to lazy command creation if session timed out after action phase * ByteArray/StringMultipartFileEditor do not log warning singleton exposure to remove singleton factory after creation of singleton object * DefaultSingletonBeanRegistry only exposes related causes on outermost creation exception (avoiding excessive logging) * Def

locally (avoiding eager init) * PropertyPathFactoryBean logs a warning if the target bean is still in creation at the time of obtaining the property * exposed public "copyRegisteredEditorsTo" method on ConfigurableBeanFactory descriptive exception if incompatible * Portlet AbstractCommandController falls back to lazy command creation if session timed out after action phase * ByteArray/StringMultipartFileEditor do not log warning singleton exposure to remove singleton factory after creation of singleton object * DefaultSingletonBeanRegistry only exposes related causes on outermost creation exception (avoiding excessive logging) * Def

explicitly ignore FactoryBeans when looking for aspect beans * reworked AspectJ auto-proxy creation to avoid the creation of unnecessary proxies * renamed ScopedObject's "remove" method to "removeFromScope" interface, allowing a post-processor to override the scope * DefaultSingletonBeanRegistry disallows the creation (or recreation) of singletons during "destroySingletons()" phase * fixed AbstractBeanFactory to XML bean definitions gets turned into a RuntimeBeanNameReference, which gets validated on bean creation * XML definitions for inner beans receive a default scope based on their containing bean (prototype

explicitly ignore FactoryBeans when looking for aspect beans * reworked AspectJ auto-proxy creation to avoid the creation of unnecessary proxies * renamed ScopedObject's "remove" method to "removeFromScope" interface, allowing a post-processor to override the scope * DefaultSingletonBeanRegistry disallows the creation (or recreation) of singletons during "destroySingletons()" phase * fixed AbstractBeanFactory to XML bean definitions gets turned into a RuntimeBeanNameReference, which gets validated on bean creation * XML definitions for inner beans receive a default scope based on their containing bean (prototype