back to a simple MBeanExporter on JDK 1.4, detecting standard MBeans * introduced "context:mbean-server" configuration element, for setting up a standalone MBeanServer reference * "context:load-time-weaver" * introduced RemoteInvocationFailureException, thrown by RMI/HTTP/JMS invoker proxies in case of server-side failure * introduced SoapFaultException, thrown by JAX-RPC/JAX-WS proxies in case of a SOAP WebSphereTransactionManagerFactoryBean uses the context class loader for compatibility with the WSAD 5.1 test server Package org.springframework.util * added "makeAccessible(Method)" and "makeAccessible(Constructor)"

configurations to PetClinic's WAR file and integration tests * PetClinic's JPA variant explicitly specifies "META-INF/orm.xml" as mapping file (for Hibernate EntityManager 3.3.0) * PetPortal's build script properly "environment-ref" attribute, pointing to a shared bean of type "java.util.Properties" * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected as Remote EJB (RMI) connect failure as well Package org ------------------------------------- General * fixed spring-beans.jar to not include "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring

configurations to PetClinic's WAR file and integration tests * PetClinic's JPA variant explicitly specifies "META-INF/orm.xml" as mapping file (for Hibernate EntityManager 3.3.0) * PetPortal's build script properly "environment-ref" attribute, pointing to a shared bean of type "java.util.Properties" * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected as Remote EJB (RMI) connect failure as well Package org ------------------------------------- General * fixed spring-beans.jar to not include "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring

configurations to PetClinic's WAR file and integration tests * PetClinic's JPA variant explicitly specifies "META-INF/orm.xml" as mapping file (for Hibernate EntityManager 3.3.0) * PetPortal's build script properly "environment-ref" attribute, pointing to a shared bean of type "java.util.Properties" * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected as Remote EJB (RMI) connect failure as well Package org ------------------------------------- General * fixed spring-beans.jar to not include "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring

back to a simple MBeanExporter on JDK 1.4, detecting standard MBeans * introduced "context:mbean-server" configuration element, for setting up a standalone MBeanServer reference * "context:load-time-weaver" * introduced RemoteInvocationFailureException, thrown by RMI/HTTP/JMS invoker proxies in case of server-side failure * introduced SoapFaultException, thrown by JAX-RPC/JAX-WS proxies in case of a SOAP WebSphereTransactionManagerFactoryBean uses the context class loader for compatibility with the WSAD 5.1 test server Package org.springframework.util * added "makeAccessible(Method)" and "makeAccessible(Constructor)"

configurations to PetClinic's WAR file and integration tests * PetClinic's JPA variant explicitly specifies "META-INF/orm.xml" as mapping file (for Hibernate EntityManager 3.3.0) * PetPortal's build script properly "environment-ref" attribute, pointing to a shared bean of type "java.util.Properties" * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected as Remote EJB (RMI) connect failure as well Package org ------------------------------------- General * fixed spring-beans.jar to not include "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring

configurations to PetClinic's WAR file and integration tests * PetClinic's JPA variant explicitly specifies "META-INF/orm.xml" as mapping file (for Hibernate EntityManager 3.3.0) * PetPortal's build script properly "environment-ref" attribute, pointing to a shared bean of type "java.util.Properties" * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected as Remote EJB (RMI) connect failure as well Package org ------------------------------------- General * fixed spring-beans.jar to not include "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring

back to a simple MBeanExporter on JDK 1.4, detecting standard MBeans * introduced "context:mbean-server" configuration element, for setting up a standalone MBeanServer reference * "context:load-time-weaver" * introduced RemoteInvocationFailureException, thrown by RMI/HTTP/JMS invoker proxies in case of server-side failure * introduced SoapFaultException, thrown by JAX-RPC/JAX-WS proxies in case of a SOAP WebSphereTransactionManagerFactoryBean uses the context class loader for compatibility with the WSAD 5.1 test server Package org.springframework.util * added "makeAccessible(Method)" and "makeAccessible(Constructor)"

"environment-ref" attribute, pointing to a shared bean of type "java.util.Properties" * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected as Remote EJB (RMI) connect failure as well Package org ----------------------------------- General * fixed spring-beans.jar to not include "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring Package org.springframework.instrument * added GlassFishLoadTimeWeaver for GlassFish / Sun Application Server * refactored Java-5-only AbstractOverridingClassLoader into JDK-1.3-compatible OverridingClassLoader

support in the Advanced Pack for Oracle Database) * added further SQL error code mapping for MS SQL Server Package org.springframework.jms * SingleConnectionFactory and TransactionAwareConnectionFactoryProxy back to a simple MBeanExporter on JDK 1.4, detecting standard MBeans * introduced "context:mbean-server" configuration element, for setting up a standalone MBeanServer reference * "context:load-time-weaver" * introduced RemoteInvocationFailureException, thrown by RMI/HTTP/JMS invoker proxies in case of server-side failure * introduced SoapFaultException, thrown by JAX-RPC/JAX-WS proxies in case of a SOAP