| Re: [jakarta.ee-community] Why not dropping EARs in Jakarta EE? |
Hi Dennis,Thanks for sharing your experience!I'm curious, do you specifically use EARs for their class isolation capabilities or just to share classes between multiple WARs at once?I assume you deploy multiple WARs in a single EAR so my proposed JPMS solution wouldn't work for you, no?_______________________________________________El dom., 29 abr. 2018 1:21, Dennis Gesker <dennis@xxxxxxxxxx> escribió:HI Ralph:Our group finds EARs extremely useful. Particularly early in the implementation of our product roadmap. Our process tends to be aggressivly iteratative. So, we prototype very quickly.Sometimes, features we initially intended to isolate (microservice but with the benefit of all the goodies of a full EE container) find their way back from a WAR back into the core EAR and vice/versa meaning elements that seemed initially to benefit from more tight coupling end up refactored our to WARs.I'd love to keep it in the standard as it provides a proven architectural approach to project assembly but doesn't prevent more modular/distributed/micro patterns.Keeping it provides utility. Keeping it doesn't prevent other patterns.BTW, I'm also in the "cheap seats" meaning not on the working group but would love to help if there is room for input/participation from small fry shops.Cordially,Dennis_______________________________________________On Sat, Apr 28, 2018, 2:07 AM 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