We are developing Java EE complaint applications since EAR appeared in the Java universe and did not have any problems with them. While we think it would be nice to simply run Microservices as standalone executable JARs, we do not see a need to remove EAR support from Jakarta EE.
-Markus (JAX-RS API Committer)
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Ralph Soika
Sent: Samstag, 28. April 2018 10:07
To: jakarta.ee-community@xxxxxxxxxxx
Subject: [jakarta.ee-community] Why not dropping EARs in Jakarta EE?
Hi,
to my background: I have been developing enterprise applications for more than 10 years, mostly as EARs. So I am mainly a User of EE and was never part of a EE working group. My opinion about EARs after years is: It's an awful disaster if you're trying to develop an ear platform independently. So why should it be called 'standard'?
Today I wonder what can be achieved with an EAR, which could not be achieved easier and clearer with a clean microservice architecture?
So I'm suggesting removing EAR support from Jakarta EE. This makes the platform easier to learn and more lightweight.
If you like, you can read the following discussion. It's about the question of how to package shared EJB libraries in one ear. And it shows how awkward it is to talk about EAR deployment questions.
https://github.com/payara/Payara/issues/2508#issuecomment-385129757
What is your opinion about the future support of the concept of EAR?
===
Ralph
