Re: [jakarta.ee-community] Why not dropping EARs in Jakarta EE?

[Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>]

I think that Jakarta EE should have profiles. Full profile should be as much backwards compatible as possible with previous version (read Java EE). It should support EARs. Other profiles (Web, Micro?) may not support EARs, or it should be up to implementations to support it.

— Dmitry

On 30 Apr 2018, at 11:55, Alexander Salvanos <salvanos@xxxxxx> wrote:

Hi all,

while I agree, that dropping EAR's feels like a good idea, for large scaled Java EE projects in huge companies, this could result into costs we could avoid, by keeping backward compatibilty.

Just like RMI-IIOP we should begin at the most with the term PROPOSED OPTIONAL and later OPTIONAL for a long period, before it can be dropped.

Best,

Alex

 

 

Gesendet: Montag, 30. April 2018 um 11:27 Uhr
Von: "Adam Bien" <abien@xxxxxxxxxxxxx>
An: "Jakarta EE community discussions" <jakarta.ee-community@xxxxxxxxxxx>
Betreff: Re: [jakarta.ee-community] Why not dropping EARs in Jakarta EE?

HI Ralph,

EARs are helpful to deploy multiple WARs at once. E.g. a main microservice with a corresponding sidecar.

However: I didn't created any EARs since Java EE 6,

cheers,

adam

> On 28. Apr 2018, at 10:06, Ralph Soika <ralph.soika@xxxxxxxxx> wrote:
>
> 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
>
> _______________________________________________
> jakarta.ee-community mailing list
> jakarta.ee-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community