I couldn't see much on the Jboss documentation. Can I use wildfly version 26.0.1 and undertow 2.2.14. Or is there a better match for Jboss 7.4?
Thanks
TL;DR
If you need the application server, it is:
WildFly 23
If you need artifacts, this is for JBoss EAP 7.4.5:
Undertow 2.2.17.SP4-redhat-00001
WildFly Core 15.0.13.Final-redhat-00001
There is also a runtime BOM for the artifacts delivered with JBoss EAP.
https://mvnrepository.com/artifact/org.jboss.bom/eap-runtime-artifacts
Long version
As Doug Grove
already described, there is an article in the Red Hat Knowledgebase that lists the different JBoss EAP versions with the integrated components. However, starting from JBoss EAP 7.x, the component versions of only one non-described JBoss EAP patch version are listed per JBoss EAP minor version.
For JBoss EAP 7.4, the article states (as of 06/22/2022):
Undertow 2.2.5.Final
WildFly Core 15.0.2.Final
If you want to have the versions for all shipped artifacts of a specific JBoss EAP patch, Red Hat offers a Maven BOM file:
https://mvnrepository.com/artifact/org.jboss.bom/eap-runtime-artifacts
For JBoss EAP 7.4.5, it states:
Undertow 2.2.17.SP4-redhat-00001
WildFly Core 15.0.13.Final-redhat-00001
(Red Hat specific versions from the Redhat GA repository)
However, it is important to note, that the listed WildFly Core version is not the same as the WildFly application server version. If you compare the version of WildFly Core used in the WildFly 23 Undertow artifact with the one in the JBoss EAP Runtime BOM, you will notice that JBoss EAP 7.4 uses the same Core as WildFly 23 application server.
https://mvnrepository.com/artifact/org.wildfly/wildfly-undertow/23.0.2.Final
Or see the POM file of WildFly 23:
https://github.com/wildfly/wildfly/blob/23.0.0.Final/pom.xml#L473
Therefore JBoss EAP 7.4 corresponds roughly to WildFly 23.
Redhat lists components for JBoss EAP 7.4 as:
Undertow 2.2.5.Final
Wildfly Core 15.0.2.Final
Is that what you are looking for?
Related
I would have added this to another thread, but I am unable to comment on other's posts. And what I read did not answer my question. I just installed EAP 7.2.0.GA. In the console log, it says:
JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001)
However, others think it is around version 13. And when I look at the releases of wildfly ( http://wildfly.org/downloads/ ) a version 6 is so old it does not even show up and would have been prior to 2014...
So, how can it be 6.0.11.Final?
WildFly core is just a component in WildFly application server.
As such is also used in JBoss EAP which is a downstream product based on WildFly AS.
WildFly core is standalone project which provides most of core capabilities (management, cli, administration, subsystem infrastructure...) of the application server without any Java EE support, that is added to it by WildFly project.
you can see the sources for both at
https://github.com/wildfly/wildfly-core/
https://github.com/wildfly/wildfly/
as for your confusion.
WildFly core 6.0.x is used in EAP 7.1 as well as in WildFly 14
which you an see also in the sources https://github.com/wildfly/wildfly/blob/14.0.0.Final/pom.xml#L375
micro version is not always exactly the same, as in the process of building downstream product of EAP, extra patches can be added.
WildFly Core is a component in JBoss Enterprise Application Platform 7 (EAP 7). So, this log means:
JBoss EAP 7.2 - JBoss EAP in version 7.2
GA - General availability
WildFly Core 6.0.11.Final - component WildFly Core in version 6.0.11.Final.
See also:
JBoss Enterprise Application Platform Component Details
Software release life cycle
Again, no information is available about this on any Red Hat or JBoss site, so I ask it here...
I am not sure if it is 13 or 14.
Mapping the Community versions with JBoss EAP versions
It is not possible to map exactly a version of the Community version
(JBoss EAP, WildFly) with the corresponding version of the supported
version (JBoss EAP) as they are maintained in separated branches. In
general terms, the following tables summarizes the version of WildFly
used as baseline for a JBoss EAP version:
JBoss EAP Version WildFly Version
JBoss EAP 7.3 WildFly 18
JBoss EAP 7.2 WildFly 14
JBoss EAP 7.1 WildFly 11
JBoss EAP 7.0 WildFly 10
JBoss EAP 6.4 JBoss AS 7.5
JBoss EAP 6.3 JBoss AS 7.4
JBoss EAP 6.2 JBoss AS 7.3
JBoss EAP 6.1 JBoss AS 7.2
JBoss EAP 6.0 JBoss AS 7.1
http://www.mastertheboss.com/jboss-server/jboss-eap/what-is-the-difference-between-jboss-eap-wildfly-and-jboss-as
I believe that it is forked from WF 13.
If you look at the module for the server core, you'll see that WF 13 uses WildFly Core 5.0.0.Final. EAP 7.2 Beta uses WildFly Core 5.0.5.
If you look at WF 14, it uses WildFly Core 6.0.2.Final, so EAP 7.2 is definitely not forked from this.
You can see the module used for the server core at: eap-install-dir/modules/system/layers/base/org/jboss/as/server/main
The versions of JBoss EAP are forked from the Wildfly projects, when certain features are complete enough they fork the project and create an EAP version.
JBoss EAP 7.0 is forked from WildFly 10
JBoss EAP 7.1 is forked from a working branch of WildFly 11
JBoss EAP 7.2 unfortunatelly has no oficial information available yet as you can see here, here and here - but I do believe it's forked from Wildfly 13 or 14, considering the last fork was Wildfly 11 and we are 3 versions ahead now.
And here is a comparative with some new information.
I am curious to know that are there any functional differences in Redhat Jboss EAP and community Wildfly. Is there something extra in EAP which is not available in Jboss wildfly.
I am using OpenShift origin with openshift wildfly centos based image. So thought of getting to know this in detail because origin doesnt provide EAP image.
WildFly is the community stream for JBoss EAP 7. Have a look at http://wildfly.org/governance/.
Can anyone please give me the main difference between JBoss AS 7 and WildFly 8?
I'm going to start a very important project and I have to choose between JBoss AS 7 and WildFly 8 (for this project I'm going to use GWT, JPA/Hibernate and jBPM 6).
WildFly 8 is the next iteration of the JBoss application server after JBoss AS 7 / EAP 6.
Basically:
JBoss AS 7.x = JEE6
JBoss EAP 6.x = JEE6
WildFly 8.x = JEE7
Red Hat typically backports security fixes from newer versions into older versions, Red Hat also typically releases "feature packs" that allow you to access newer features/specs.
So if it is a very important project and you do not need JEE7 specs, you may want to use JBoss EAP which is the productized version of JBoss AS 7.
Otherwise you may want to use WildFly if you need the more cutting edge specs and features.
Related
See JBoss AS / WildFly versions history for more details.
WildFly is the new name of JBoss AS so that the company JBoss and the application server JBoss cannot induce confusion anymore.
Think of WildFly 8 as JBoss AS 8, just with a different name.
JBoss 7 is an implementation of JavaEE 6.
WildFly 8 is an implementation of JavaEE 7.
The JBoss application server is the "commercialized" version of the community Wildfly application server. Red Hat offers support contracts for JBoss and has a long term maintenance schedule for JBoss.
The versions are also different. JBoss EAP 6 corresponds to Wildfly 7.
I am currently in the phase of migrating my Clustered Application from Jboss eap 5.1 to Jboss eap 6.1 (Jboss AS 7.1). The jboss eap 6.1 uses HornetQ as its JMS system as compared to Jboss eap 5.1 which used JBoss MQ as JMS system. My application has the requirement of using global and local JMS topics(distributed and non-distributed topics). On jboss eap 5.1, there is a configuration file in the messaging folder called 'xxx-destination-service.xml' which provided a boolean attribute called 'Clustered' defined for each of the JMS topics. This xml file and the attribute is no longer supported in jboss eap 6.1. Can anyone provide me pointers on how this can be done in jboss eap 6.1.
I am Clustering my application in Domain Mode on Jboss eap 6.1 . So please tell what configuration chnages need to be done in my domain.xml or any other xml file.
TIA for your help.
Ajit