{"id":18603,"date":"2022-08-22T09:52:15","date_gmt":"2022-08-22T07:52:15","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=18603"},"modified":"2022-08-22T09:52:15","modified_gmt":"2022-08-22T07:52:15","slug":"redhat-jboss-eap-8-is-on-the-way","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/redhat-jboss-eap-8-is-on-the-way\/","title":{"rendered":"RedHat JBoss EAP 8 is on the Way"},"content":{"rendered":"\n

As recently published<\/a>, RedHat planned to release a new JBoss EAP version: Release 8<\/strong>. A beta release is planned in Q2 this year when official release is tentatively planned in first semester 2023. One might think it is a too early to look at it, but as you know JBoss is downstream of upstream<\/a> open source project Wildfly. Let’s look at the history to understand features and Java standards compatibilities.<\/p>\n\n\n\n

Versions Mappings<\/h2>\n\n\n\n

To lay the foundation, we have to look at where we are with current Release:<\/p>\n\n\n\n

JBoss EAP Version<\/strong><\/td>Wildfly Version<\/strong><\/td><\/tr>
7.4<\/td>23<\/td><\/tr>
7.3<\/td>18<\/td><\/tr>
7.2<\/td>14<\/td><\/tr>
7.1<\/td>11<\/td><\/tr>
7.0<\/td>10<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

JBoss and Wildfly are based on Java standards currently known as Jakarta EE. Jakarta EE is a set of specifications extending Java SE with versions mapping as follow:<\/p>\n\n\n\n

Platform Version<\/strong><\/td>Specifications<\/strong><\/td>Java SE Support<\/strong><\/td><\/tr>
Jakarta EE 10<\/td>10<\/td>17, 11<\/td><\/tr>
Jakarta EE 9.1<\/td>9.1<\/td>11, 8<\/td><\/tr>
Jakarta EE 9<\/td>9<\/td>8<\/td><\/tr>
Jakarta EE 8<\/td>8<\/td>8<\/td><\/tr>
Java EE 8<\/td>JSR 366<\/td>8<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

As you can see, Java Enterprise Edition (EE) was renamed to Jakarta EE on release 8. <\/p>\n\n\n\n

Jakarta EE 9 contains mainly a renaming of the javax.* to jakarta.* namespace. This have an importance for your application to run smoothly whether it is developed internally or out-of-the-box. On his side, RedHat decided to bypass the support of Jakarta EE 9 as JBoss EE 8 will go directly to Jakarta EE 10.<\/p>\n\n\n\n

To summarize as a table:<\/p>\n\n\n\n

JBoss EE Version<\/strong><\/td>Wildfly Version<\/strong><\/td>Platform Version<\/strong><\/td><\/tr>
8<\/td>27<\/td>Jakarta EE 10<\/td><\/tr>
7.4<\/td>23<\/td>Jakarta EE 9.1<\/td><\/tr>
<\/td><\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

JBoss EAP 8 will be based on Wildfly 27 (currently in Alpha) which means we can test the new features right now. Of course, until JBoss is released this is subject to change.<\/p>\n\n\n\n

JBoss EAP Version 8 Features<\/h2>\n\n\n\n

The main improvement, as specified in Jakarta EE, is the introduction of a new Core profile<\/strong>. This profile is lighter for the need of the container world (microservices and serverless architectures) to be able to spin up extra instances faster. So, additionally to the existing out-of-the-box standalone profiles, Wildfly adds two new profiles:<\/p>\n\n\n\n