In WildFly, MicroProfile API are available out of the box in the full server distribution.The binaries of JBoss EAP and WildFly are available at the following locations:īuilding MicroProfile applications using EAP and WildFlyĪnother key difference between JBoss EAP and WildFly relates to the development of MicroProfile applications. The source code of JBoss EAP and WildFly are available on Github. However, the following table shows which WildFly version is the baseline to build a JBoss EAP version: JBoss EAP Version This is due to the fact that they are maintained in separated branches. Mapping WildFly versions with JBoss EAP versionsįirstly, it is not possible to map exactly a version of the Community version ( WildFly) with the corresponding version of JBoss EAP. The following Java EE versions are supported in the latest versions of the application server: Application Server Version
More about this topic on the following article: Is JBoss EAP free to use ? Some differences in functionality, security patches, etc. That does not mean that the source codes for both projects are identical. IMPORTANT NOTICE: JBoss EAP derives from the source code of WildFly. You can download JBoss EAP from the following link: JBoss EAP is still an opensource project but if you want to use JBoss EAP in production with Red Hat’s support, then you need to activate a subscription. JBoss Enterprise Application platform is Red Hat’s supported application server. You can get help at various levels:ġ) Through the Forum currently hosted in a Google Group !forum/wildflyĢ) Using StackOverFlow, setting as item “wildfly”: How to receive Enterprise support: JBoss EAP IMPORTANT NOTICE: Wildfly application server is not supported as a product by Red Hat.
So, since the version 27, WildFly is a Jakarta EE 10 Full/Core/Web platform compatible implementation. Please note that WildFly 27 has passed the Jakarta EE 10 TCK and its compatibility certification request has been approved by the Jakarta EE Spec Committee. In the following table you can see the Java EE / Jakarta EE Compatibility Matrix for each version of the Community application server: Application Server Version For example by reporting bugs or submitting Pull Requests on the WildFly Project (available on Github ). Likewise, we recommend to be an active member of WildFly community if you want to deploy WildFly in an Enterprise context. On the other hand, if you are planning to do that, you are strongly advised to migrate to the latest version of WildFly, as those versions are not maintained by any community of developers.
0 kommentar(er)
