GlassFish, an open source Jakarta EE Platform implementation, is a code base that goes back a long time, in essence all the way back to 1996. It’s also a fairly large code base. Therefor it’s not surprising perhaps that in all that time it obtained some cruft between all those lines of code, which made it challenging to run on modern versions of the JDK.
…Last year we started a survey about Jakarta EE.
In this survey we asked several questions about Jakarta EE, what people use exactly, and what they would like to see next. The survey was promoted in September 2022. The survey was left alone for the next months, until a little promotion was done towards the end of the year. In total we ended up with 720 respondents in total, which is slightly up from the 684 we got last time.
…
Enterprise Beans was once the face of Java EE, but as we discussed a while ago, is currently de-emphasised in Jakarta EE. However, since there’s so much existing code using Enterprise Beans, a certain level of support is still desired.
Piranha Cloud, a relatively new runtime supporting Jakarta EE, takes a somewhat novel approach to Enterprise Beans. Instead of implementing a separate container, Piranha Cloud, via the OmniBeans project, maps Enterprise Beans annotations to equivalent functionality in CDI itself, or to technologies in Jakarta EE leveraging CDI (such as Jakarta Transactions). Enterprise Beans features not currently present in Jakarta EE, such as the pooled concept for Stateless beans, are provided by the OmniServices library.
…
EJB, or Enterprise Beans, are Java classes with a number of container provided services attached to them, such as transactions, remoting and security. In this article we will take a look at what we can expect for EJB in the future.
Once upon a time EJB was almost synonymous with what was called Java EE or J2EE back then (Jakarta EE now). It suffered from many issues though, although it did incrementally got better. We’ll explore some of those issues next.
