getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

getPackage()" * MBeanClientInterceptor automatically converts MXBean CompositeData/TabularData structures according to Java 5/6 rules * MBeanClientInterceptor uses the standard JDK MBeanServerInvocationHandler spring-web.jar contains web-related remoting and ORM classes (for proper use in J2EE EAR deployment structures) * renamed spring-dao.jar to spring-tx.jar, also containing the JCA support now * renamed spring-support methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type

integral to the Spring Framework. Foremost amongst these is the Spring Framework’s Inversion of Control (IoC) container. A thorough treatment of the Spring Framework’s IoC container is closely followed Spring’s Inversion of Control (IoC) container. 1.1. Introduction to the Spring IoC Container and Beans This chapter covers the Spring Framework implementation of the Inversion of Control (IoC) principle when it creates the bean. This process is fundamentally the inverse (hence the name, Inversion of Control) of the bean itself controlling the instantiation or location of its dependencies by using direct

methods to Constants * fixed GenericCollectionTypeResolver to correctly navigate Map-List-List structures with a nesting level of 3 or more * BridgeMethodResolver performs multi-step resolution of type startup * AbstractAdvisorAutoProxyCreator performs BeanFactory-based prototype cycle check instead of control flow check Package org.springframework.beans * factored out SingletonBeanRegistry interface from values across parent/child definitions * added "default-merge" attribute to "beans" element to allow control of collection merging at the file level * changed FileEditor's behavior to consider input text as