Java EE 6 behavior differences
Java EE 6 might introduce some behavior differences in your application because of implementation changes and specification clarifications.
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Use HttpServletRequest logout method for programmatic security logout in Servlet 3.0 |
Do not rely on the HttpSession invalidate method for programmatic security logout. Add the HttpServletRequest logout method which was introduced in Java EE 6 as part of the Servlet 3.0 specification. |
java-version-17.yml org.openrewrite.java.migrate.javax.HttpSessionInvalidate |
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Java Persistence API (JPA) | This rule flags references to javax.persistence packages. The WebSphere default JPA provider switched from OpenJPA for JPA 2.0 (Java EE 6) to EclipseLink for JPA 2.1 (Java EE 7). |
No |
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Java API for RESTful Web Services (JAX-RS) | This rule flags references to javax.ws.rs packages. | No |
In Liberty and WebSphere Application Server traditional V9.0, you can use JAX-RS 1.1 or JPA 2.0 instead of the updated versions of these technologies that were implemented in Java EE 7. If you do not run the Java EE 7 migration rules for either JAX-RS or JPA technologies, the Java EE 6 rules remind you to configure the server to use the Java EE 6 implementation.