Package org.springframework.beans * revised GenericTypeAwarePropertyDescriptor for compatibility with IBM's JDK 1.6 (avoiding NPE) * TypeMismatchException shows type description for mismatching JDK proxy DatabaseMetaData Connection if non-null (for WebLogic cluster compatibility) * fixed SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error compatibility * SimpleRemoteSlsbInvokerInterceptor properly detects CORBA connect failures on the IBM JVM (for WebSphere EJB access) Package org.springframework.instrument * added public "isInstrumentationAvailable()"

Package org.springframework.beans * revised GenericTypeAwarePropertyDescriptor for compatibility with IBM's JDK 1.6 (avoiding NPE) * TypeMismatchException shows type description for mismatching JDK proxy DatabaseMetaData Connection if non-null (for WebLogic cluster compatibility) * fixed SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error compatibility * SimpleRemoteSlsbInvokerInterceptor properly detects CORBA connect failures on the IBM JVM (for WebSphere EJB access) Package org.springframework.instrument * added public "isInstrumentationAvailable()"

Package org.springframework.beans * revised GenericTypeAwarePropertyDescriptor for compatibility with IBM's JDK 1.6 (avoiding NPE) * TypeMismatchException shows type description for mismatching JDK proxy DatabaseMetaData Connection if non-null (for WebLogic cluster compatibility) * fixed SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error compatibility * SimpleRemoteSlsbInvokerInterceptor properly detects CORBA connect failures on the IBM JVM (for WebSphere EJB access) Package org.springframework.instrument * added public "isInstrumentationAvailable()"

DatabaseMetaData Connection if non-null (for WebLogic cluster compatibility) * fixed SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error compatibility * SimpleRemoteSlsbInvokerInterceptor properly detects CORBA connect failures on the IBM JVM (for WebSphere EJB access) Package org.springframework.instrument * added public "isInstrumentationAvailable()" ConcurrencyFailureException * SQLErrorCodesSQLExceptionTranslator falls back to SQL state translation for IBM DB2 and MS SQL by default * added further default "sql-error-codes.xml" mappings for MS SQL, MySQL

DatabaseMetaData Connection if non-null (for WebLogic cluster compatibility) * fixed SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error compatibility * SimpleRemoteSlsbInvokerInterceptor properly detects CORBA connect failures on the IBM JVM (for WebSphere EJB access) Package org.springframework.instrument * added public "isInstrumentationAvailable()" ConcurrencyFailureException * SQLErrorCodesSQLExceptionTranslator falls back to SQL state translation for IBM DB2 and MS SQL by default * added further default "sql-error-codes.xml" mappings for MS SQL, MySQL

compatibility * SimpleRemoteSlsbInvokerInterceptor properly detects CORBA connect failures on the IBM JVM (for WebSphere EJB access) Package org.springframework.instrument * added public "isInstrumentationAvailable()" ConcurrencyFailureException * SQLErrorCodesSQLExceptionTranslator falls back to SQL state translation for IBM DB2 and MS SQL by default * added further default "sql-error-codes.xml" mappings for MS SQL, MySQL JdbcTemplate falls back to type VARCHAR for a null value in case of an unknown SQL type specified against IBM DB2 * JdbcTemplate uses "PreparedStatement.setString" in case of LONGVARCHAR and CLOB (if given a

annotations) * MethodParameter uses reflection to obtain parameter annotations (for compatibility with the IBM 1.4.2 VM's debug mode) * LocalVariableTableParameterNameDiscoverer caches parameter names per method ClassFileTransformers (makes AspectJ LTW work) * ShadowingClassLoader excludes the "com.ibm." package by default as well (for IBM JDK classes, DB2 JDBC driver, etc) Package org.springframework.jdbc * fixed JdbcUtils on Java EE 5) * added WebSphereUowTransactionManager, supporting full transaction management via IBM's UOWManager API on WAS 6.0/6.1 * removed WAS 4.0/5.0 support from WebSphereTransactionManagerFactoryBean

Spring can be consistently used on application servers such as BEA WebLogic 8.1, 9.0, 9.2 and 10, IBM WebSphere 5.1, 6.0, 6.1 and 7, Oracle OC4J 10.1.3 and 11, JBoss 3.2, 4.0, 4.2 and 5.0, as well as Tomcat Framework (2.5.6) 23 2.4.2. Full WebSphere transaction management support Spring 2.5 explicitly supports IBM's WebSphere Application Server, in particular with respect to WebSphere's transaction manager. Transaction Spring 2.5's WebSphereUowTransactionManager as your PlatformTransactionManager of choice. This is also IBM's official recommendation. For automatic detection of the underlying JTA-based transaction platform

Spring can be consistently used on application servers such as BEA WebLogic 8.1, 9.0, 9.2 and 10, IBM WebSphere 5.1, 6.0 and 6.1, Oracle OC4J 10.1.3 and 11, JBoss 3.2, 4.0 and 4.2, as well as Tomcat 4 the details. 2.4.2. Full WebSphere transaction management support Spring 2.5 explicitly supports IBM's WebSphere Application Server, in particular with respect to WebSphere's What's new in Spring 2.0 Spring 2.5's WebSphereUowTransactionManager as your PlatformTransactionManager of choice. This is also IBM's official recommendation. For automatic detection of the underlying JTA-based transaction platform

Spring can be consistently used on application servers such as BEA WebLogic 8.1, 9.0, 9.2 and 10, IBM WebSphere 5.1, 6.0 and 6.1, Oracle OC4J 10.1.3 and 11, JBoss 3.2, 4.0 and 4.2, as well as Tomcat 4 the details. 2.4.2. Full WebSphere transaction management support Spring 2.5 explicitly supports IBM's WebSphere Application Server, in particular with respect to WebSphere's What's new in Spring 2.0 Spring 2.5's WebSphereUowTransactionManager as your PlatformTransactionManager of choice. This is also IBM's official recommendation. For automatic detection of the underlying JTA-based transaction platform