I don’t see the point of retiring EJB(lite) from Web profile before Full profile.
If we are intending to send the message “that EJB (lite) is a stable technology intended for legacy workloads” then a retirement roadmap should be developed from the Full profile as well as
the Web profile simultaneously. Full profile should not be treated as a dumping ground “legacy” profile.
We have Core profile where implementations are free to ship Core profile(+) if they want to have a Jakarta EE compatible “legacy free” runtime. More logical would be to actually retire Web profile and keep Core profile and Full profile,
although I am not advocating for this. Reality is most Payara customers choose Full profile over our Web profile product.
Btw I don’t agree with the messaging that EJB is legacy as there is no current replacement. Jakarta EE developers out there are still building new applications using @Stateless as it just works and is simpler than the current alternative.
I agree CDI needs to become the foundational “bean” component for the platform but it isn’t there yet.
Steve
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of arjan tijms
Sent: 12 August 2022 14:02
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Retire EJB-Lite from web profile?
Hi,
As it's probably a decade long effort to actually prune it in every way, it might be a good idea to start the process now.
It's perhaps a little like the Entity Beans and the EJB 2.x API group, as well as Corba and aspects of remote EJB, of which the process started around 2009. 13 years later, even just a few days ago, TCKs are still
being adjusted for this.
GlassFish would likely not ship EJB-Lite if it was removed (as GF has historically never shipped a Web profile plus), and Piranha would likely not include EJB-lite in a web profile distribution (though may still
provide EJB-Lite features in other distributions, some of which are dynamic (on demand loading of features).
More importantly, I think, is the signal that EJB (lite) is a stable technology intended for legacy workloads, and not so much for any new code.
I have another question in mind.
Would some other runtimes that implement some Jakarta EE specifications, be interested in certifying against Web Profile if EJB lite was removed? I'm thinking about Quarkus here, which doesn't provide EJB but
provides a lot of other Jakarta EE APIs. However, Quarkus would still miss support for example for CDI portable extensions, JSP, Jakarta Security, and probably some other things as well.
So, would removing EJB from Web Profile motivate more runtimes/frameworks to become Web Profile compatible? If not, should we aim to remove some more Web Profile features to make it easier to become compatible?
Or is it enough to provide Jakarta Core profile and leave Web Profile as it is?
All the best,,
Director, Jakarta EE expert
Omnifish OÜ, Narva mnt 5, 10117 Tallinn, Estonia | VAT: EE102487932
Payara would still ship it in Web Profile until EJB was removed from Full profile.
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
Perhaps the best way to frame up this conversation is to get a simple yes/no answer from implementors.
Would you still ship EJB-lie if it was marked "not required, but still can be shipped"?
For us the answer is definitely, yes we would still ship it.
Hi,
With Concurrency being added to the web profile of Jakarta EE 10, and the focus in Jakarta EE 10 dramatically having shifted away from EJB and towards CDI, do we still need EJB-Lite in the web profile?
Obviously vendors can still add EJB-Lite to their web profile offering, just as the sole web-profile only product does today, but should EJB-Lite still be a requirement going forward for EE 11?
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|
