* upgraded to Hibernate 3.3.0 (while retaining compatibility with Hibernate 3.1/3.2) * upgraded to iBATIS SQL Maps 2.3.2 (while retaining compatibility with iBATIS 2.3.0) Package org.springframework replacement values Package org.springframework.beans * revised GenericTypeAwarePropertyDescriptor for compatibility with IBM's JDK 1.6 (avoiding NPE) * TypeMismatchException shows type description for mismatching interfaces) * CustomNumberEditor explicitly removes all inline whitespace from input Strings (for compatibility with French locales) * added "getDescription()" method to BeanDefinition interface (exposing the

Build an executable archive with Ant How to use Java 6 Embedded servlet container compatibility JTA API compatibility 74. Traditional deployment Create a deployable war file Create a deployable war file executable jar file structure The executable war file structure Spring Boot’s “JarFile” class Compatibility with the standard Java “JarFile” Launching executable jars Launcher manifest Exploded archives Changing the Java version The spring-boot-starter-parent chooses fairly conservative Java compatibility. If you want to follow our recommendation and use a later Java version you can add a java.version

Build an executable archive with Ant How to use Java 6 Embedded servlet container compatibility JTA API compatibility 74. Traditional deployment Create a deployable war file Create a deployable war file executable jar file structure The executable war file structure Spring Boot’s “JarFile” class Compatibility with the standard Java “JarFile” Launching executable jars Launcher manifest Exploded archives Changing the Java version The spring-boot-starter-parent chooses fairly conservative Java compatibility. If you want to follow our recommendation and use a later Java version you can add a java.version

Build an executable archive with Ant How to use Java 6 Embedded servlet container compatibility JTA API compatibility 74. Traditional deployment Create a deployable war file Create a deployable war file executable jar file structure The executable war file structure Spring Boot’s “JarFile” class Compatibility with the standard Java “JarFile” Launching executable jars Launcher manifest Exploded archives Changing the Java version The spring-boot-starter-parent chooses fairly conservative Java compatibility. If you want to follow our recommendation and use a later Java version you can add a java.version

Build an executable archive with Ant How to use Java 6 Embedded servlet container compatibility JTA API compatibility 74. Traditional deployment Create a deployable war file Create a deployable war file executable jar file structure The executable war file structure Spring Boot’s “JarFile” class Compatibility with the standard Java “JarFile” Launching executable jars Launcher manifest Exploded archives Changing the Java version The spring-boot-starter-parent chooses fairly conservative Java compatibility. If you want to follow our recommendation and use a later Java version you can add a java.version

Build an executable archive with Ant How to use Java 6 Embedded servlet container compatibility JTA API compatibility 74. Traditional deployment Create a deployable war file Create a deployable war file executable jar file structure The executable war file structure Spring Boot’s “JarFile” class Compatibility with the standard Java “JarFile” Launching executable jars Launcher manifest Exploded archives Changing the Java version The spring-boot-starter-parent chooses fairly conservative Java compatibility. If you want to follow our recommendation and use a later Java version you can add a java.version

(2008-04-28) ------------------------------------- General * upgraded to AspectJ 1.6 (while retaining compatibility with AspectJ 1.5.x) * fixed spring-core.jar's manifest to contain correct OSGi Import-Package PathMatchingResourcePatternResolver resolves encoded jar URIs before creating JarFiles (for WebSphere compatibility) * PathMatchingResourcePatternResolver catches NoClassDefFoundError when looking for presence SimpleMetadataReaderFactory uses ResourceLoader's ClassLoader for loading annotation classes (for OSGi compatibility) Package org.springframework.jdbc * JdbcTemplate explicitly detects and skips null ResultSets

2 (retaining compatibility with AspectJ 1.5.x and 1.6.x) * upgraded to EHCache 1.5.0 (retaining compatibility with EHCache 1.2 and higher) * upgraded to TestNG 5.8 (retaining compatibility with TestNG 5 5.5 and higher) * upgraded to OpenJPA 1.1.0 (retaining compatibility with OpenJPA 1.0.x as well as 1.2.0) * upgraded to EclipseLink 1.0.1 (EclipseLinkJpaVendorAdapter requires EclipseLink 1.0.0+ now) HibernateJpaDialect checks "EntityManager.getDelegate()" as well to find Hibernate Session (for Seam compatibility) * added "persistenceXmlLocation" property to DefaultPersistenceUnitManager, as alternative to

2 (retaining compatibility with AspectJ 1.5.x and 1.6.x) * upgraded to EHCache 1.5.0 (retaining compatibility with EHCache 1.2 and higher) * upgraded to TestNG 5.8 (retaining compatibility with TestNG 5 5.5 and higher) * upgraded to OpenJPA 1.1.0 (retaining compatibility with OpenJPA 1.0.x as well as 1.2.0) * upgraded to EclipseLink 1.0.1 (EclipseLinkJpaVendorAdapter requires EclipseLink 1.0.0+ now) HibernateJpaDialect checks "EntityManager.getDelegate()" as well to find Hibernate Session (for Seam compatibility) * added "persistenceXmlLocation" property to DefaultPersistenceUnitManager, as alternative to

.................. 180 Embedded servlet container compatibility ......................................................... 180 JTA API compatibility .................................................. “JarFile” class ............................................................................. 205 Compatibility with the standard Java “JarFile” ................................................... 205 D.3 Changing the Java version The spring-boot-starter-parent chooses fairly conservative Java compatibility. If you want to follow our recommendation and use a later Java version you can add a java.version