tomcat - JBoss AS vs WildFly 8





tutorial 11 (5)


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.

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).




I've tested both, JBoss 7.1.1 AS and WildFly 8.2.1 and I think that is mostly seems at the last one. If you check the dates, JBoss EAP 6.4 and WildFly 8 are parallels in 2015 but JBoss 7 has stopped in 2012.




What Is The Wildfly Equivalent Of JBoss EAP 6.4

The closest version you will find is JBoss AS 7.1.1. This is very similar to EAP 6.4 but not exact. EAP 6.4 exact match would be closer to AS 7.5 but a binary for that has never been released. (You can build it yourself from source)

I would try 7.1.1 and see if it works. Moving to Wildfly 8 is a bigger change and I wouldn't expect it to work out of the box unless the vendor supports WF/EAP 7.

I also noticed that JBoss AS 7.2.0 is in maven central but not released on their web page. You might want to try this out and see if it works.

The Maven Cargo plugin gives a good description of the versions - although as mentioned above, not all binaries are available to download.

JBoss EAP version 6.1 = the build from JBoss AS version 7.2 released in May 2013
JBoss EAP version 6.2 = the build from JBoss AS version 7.3 released in October 2013
JBoss EAP version 6.3 = the build from JBoss AS version 7.4 released in June 2014
JBoss EAP version 6.4 = the build from JBoss AS version 7.5 released in October 2015



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.




I have also read that for some servers one for example needs only annotate persistence contexts, but in some servers, the injection should be done manually.