I recently had to run a feasibility check to upgrade an application from Jboss 7 to Jboss 8 . Documenting the min required compatible versions & the rationale here in case it helps anyone using similar tech stack.
Tech stack:
| Current Tech | Version | Tech Required for Jboss 8 | Version |
|---|---|---|---|
| Java | 1.8 | Java | 17 |
| Java EE | 8 | Jakarta EE | 9+ |
| Spring | 2.5.6 | Spring | 6.0.x |
| Struts | 1.x | Spring MVC | 6.0.x |
| Jboss | 7.1 | Jboss | 8 |
Rationale for Java 17 :
- The lowest supported Java version for Jboss 8 is Java 11.
- The baseline supported version for Spring 6.x is Java 17.
Rationale for Jakarta EE 9+ :
| Jakarta EE version | Package names | Description |
|---|---|---|
| Jakarta EE 8 | javax.* | Same as Java EE 8 only the brand name has been updated. No change in namespace. |
| Jakarta EE 9 | jakarta.* | Brand names & package names are updated. Namespace changed to jakarta. |
| Jakarta EE 10 | jakarta.* | Brand names & package names are updated along with changes to the API itself. |
Rationale for Spring 6.0.x :
| Spring version | Supported Jakarta EE version | JDK version |
|---|---|---|
| Spring Framework 5.3.x | Java EE 7 - 8 | JDK 1.8 - 21 |
| Spring Framework 6.0.x | Jakarta EE 9 - 10 | JDK 17 - 21 |
Rationale for Spring MVC 6.0.x :
Struts 7.0.0 release version supporting Jakarta EE 9+ has not been released yet according to WW-5141
Top comments (0)