JBoss is now using version 6.1.0 EAP (Alpha+), after the release of 7.1.1 AS.
It’s important to point out that JBoss has carried out several adjustments to its versioning policy since the release of version 7.1.1 AS (community), to the subsequent 6.1.0 EAP (Enterprise). While these changes might be confusing to developers, they’re justified because the Community version was falling far behind the needs of the applications which are currently being developed, and JBoss is very interested in improving its service. According to RedHat, version 6.1.0 EAP is of much higher quality, even though it’s still only in its Alpha version. It’s also worth noting that this version boasts an LGPL license and should coincide with version 7.2.0AS, which will be ignored from here on in.
In the following paragraphs, we’ll highlight the advantages and disadvantages of this version. Note that this evaluation of good and bad things is based on version 7+ (which coincides with 6.1.0 EAP, with errors fixed.)
Advantages of JBoss 6.1.0 EAP
- Certified in Java EE 6 (5.1 uses Java EE 5 and 6.0 uses uncertified Java EE6).
- Starts up to 10 times faster than previous versions.
- Improved administration system. New command console.
- Uses fewer resources. Manages memory better when applications are opened.
- Simpler configuration, both with application configuration and the middleware center.
- Noteworthy: (OSGI) More modular design. Isolation at the application level for the use of global libraries (Load classes on demand). Much easier deployments.
- Noteworthy: JBoss Seam 3 + CDI + Weld deployment (currently uses Seam 2).
- Cool: Includes JSF2 (Currently uses JSF1).
Disadvantages of JBoss 6.1.0 EAP
- Performance problems with EJB shared among servers.
- Performance problems and use saturation of EJB on the client and on the server side
- Use of unnecessary global services in deployment, which negatively affects performance, memory and disk space.
- Migration to version 6.1.0EAP (7.2AS) would generally have a lot more positive points than negative ones for the deployment and its use of libraries and API are much more advanced, counting on fundamentally better JSF + SEAM.
- Modularization allows for much simpler deployment to configure, which, up until now, we’ve gained in performance.
- Use on the administrative level is a lot easier for systems administrators to control.
- With regard to use high-capacity EJB use, we should pay attention to its performance, keeping in mind that a lot of bugs have been fixed in version 6.1.0EAP.
This analysis has been carried out by our amazing Víctor Sánchez (@victors), Head of R&D. Ask any question you’d like on our blog, or via our Twitter feed @athento.
Has this post been useful? Don’t forget to share it with the community