Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] R: R: Should we consider rebasing Enterprise Beans Lite to a mapping/extension on top of CDI?

MP REST Client lacks on maintenance at the moment unfortunately (the current version is depending on Jakarta 9.x versions of the component specs).
There is also a test gap between MP JWT and MP REST Client (which should be solved in the first one on my opinion).

But the discussed approach of creating a replacement for EJB Lite could create a good reason for moving it to Jakarta (REST?) and get it supported there.
A challenge might be the organisational aspect of it, but why not learn and improve this.


Am 13.08.23 um 22:43 schrieb Arjan Tijms via jakartaee-platform-dev:

On Sat, 12 Aug 2023 at 21:07, Doyle, James, K via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:

 Other EJB-related features are useful to our applications also (declarative/annotated transactions, declarative/annotated security, lifecycle management and pooling, tuning parameters like timeouts).

Declarative/annotated transactions can be done via Jakarta Transactions.

Declarative/annotated security can be done (partially will be done) by Jakarta Security.

Lifecycle management is done by CDI.

Pooling is something we've yet to add to a Jakarta API. We've prototyped a CDI compatible scope for it here:

Kind regards,
Arjan Tijms

jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top