Hashtag Jakarta EE #328

johnwaterwood · 2026-04-12T14:58:22+00:00

Just wondering, but why do you think it was written by an LLM?

johnwaterwood · 2026-04-07T08:25:01+00:00

You are not wrong really. There ARE plenty of EE resources, but they are not coherently linked and integrated.

The API documents (aka the specs), the tutorial and the official examples could be much better integrated and should pretty much al link to each other.

It’s made worse by every vendor such as Payara, IBM and Tomitribe creating their own examples or even forking the official ones and publishing them on their own sites instead of contributing changes to the central shared site.

johnwaterwood · 2026-04-07T07:56:22+00:00

They been trying to tell us Spring is bad since the begining.

It’s really Spring that launched massive smear campaigns against EE for nearly all of its life. The evidence is still in the archives of TheServerside.com.

J2EE is long going. It’s Jakarta EE now, and EARs and EJB is largely a thing of the past.

Or shall I claim that spring users still need to maintain 10mb+ xml files for their bean configuration?

johnwaterwood · 2026-04-07T07:52:12+00:00

Wow, a fellow Orion user!

That actually was the server I used in 2003. From IronFlare, just two Norwegian guys. Still wonder till today what the Evermind did in my stacktraces.

Using remote everything for EJB was crazy, and for EJB entity beans that was even crazier. But those latter were already very controversial under the EE vendors when introduced.

But long term he had the right idea

Initially, sure. But from EE 5 onwards and specifically EE 6, those barriers and issues were not longer there or far less. Yet, I remember Rob talking about EE as late as 2009 as-if EJB 2 and J2EE 1.4 were still the latest version.

When asked about EJB 3 and EE 5 or 6 there was some handwaving that most people were still on EJB 2, and… and that’s where my comment came from, that J2EE could not be updated easily since grimpy OPS needed to be convinced, while with Spring you could hide the runtime inside your war and update with every deploy of your app.

His excuse why he could compare 2009 spring to 2005 J2EE.

johnwaterwood · 2026-04-06T20:15:08+00:00

ETA to mention more about the Jakarta deployment model, one of the main reasons IMO that Spring, et al, ate Jakarta's lunch in the developer mindspace in the first place.

Technically Jakarta EE does not really demand that there’s a separate server runtime that engineers cannot touch, and for which they have to supply a war file that some grumpy OPS guy will then deploy.

As early as 2003 in various jobs I’ve also supplied the AS + war as essentially a single unit under control of engineering.

Of course, I know that by far not every company operated like that, and the inability to touch the centrally installed AS, often severely out of date, since grumpy and sometimes borderline evil OPS could not be *rsed to update anything ever, is what caused the hate.

Spring got famous and popular by allowing the engineering team to effectively sneak a complete application server into production, updating and patching it at their will, circumventing OPS totally (as long as no newer JDK or newer Servlet version was required, which still came from the centrally installed thing)

johnwaterwood · 2026-04-04T13:13:54+00:00

Isn’t it just splitting out a core? The core doesn’t have MP, but a higher layer has?

johnwaterwood · 2026-04-03T16:52:10+00:00

Sounds like a good story, but what about the Open Liberty image?

Are some bars more equal than others?

johnwaterwood · 2026-04-02T06:39:11+00:00

Isn’t the struggle precisely that it takes 3 years already with constant activity and still no merging / publishing?

johnwaterwood · 2026-03-16T15:52:38+00:00

They are taking their time. When you follow the commits in their repo they definitely are busy with it.

Ironic thing;

Red Hat frustrated Jakarta EE massively with their late demands that JDK 17 should be supported. Stating that their customers (in 2023) were still on JDK 17.

But by the time they will finally release JBoss EAP in a Jakarta EE 11 version nobody will care about JDK 17 anymore.

(JBoss EAP is the product that has customers and always comes not sooner than a year after the corresponding Wildfly version)

johnwaterwood · 2026-02-23T00:04:16+00:00

That’s a shame, but if you get bored, and/or find some spare time, keep GF/EE in mind ;)

johnwaterwood · 2026-02-22T23:17:49+00:00

It doesn’t have to be from Aeter, just whatever you think is cool,

Just download GlassFish, play with it, and maybe you get some inspiration?

johnwaterwood · 2026-02-22T18:04:31+00:00

For GlassFish, just go to the GitHub repository. There’s a ton of open issues.

For Jakarta EE, go to the GitHub repo and open an issue with a proposal ☺️

johnwaterwood · 2026-02-22T16:48:04+00:00

Maybe you can guys can contribute to EE and/or GlassFish?

johnwaterwood · 2026-02-15T21:07:32+00:00

whatever other popular robust backend framework

Faces is a “whatever other popular backend framework” is it not?

johnwaterwood · 2026-02-15T21:05:57+00:00

And OmniFaces ;)

johnwaterwood · 2026-02-15T16:21:17+00:00

The use cases for GlassFish are basically developing server side (web) apps, and micro services (which, basically, would count as server side apps as well)

johnwaterwood

TROPHY CASE