For future Jakarta EE new versions, I think EJB should not be marginalized.

[lairoea-web]

For future new versions of Jakarta EE, I don't think EJB should be marginalized. I believe the soul of Jakarta EE lies in EJB. The EJB originally created by Sun is truly charming. EJB is the core, and I think we should enhance and perfect its features — for example, adding stronger AOP capabilities and optimizing the container to make performance take off.
This is just my personal suggestion. I hope my thoughts can be heard. Thank you

[lairoea-web]

I personally find EJB quite appealing and elegant. It was a visionary concept originally introduced by Sun Microsystems. In my view, enterprise-level Java EE applications have always relied heavily on EJB.
I believe that future versions of Jakarta EE should not marginalize EJB. It remains the very soul of the Jakarta EE platform. If EJB were to be sidelined, Jakarta EE would lose much of what distinguishes it from frameworks like Spring.
After all, true enterprise solutions are meant to be robust and comprehensive — and that’s precisely where EJB’s charm lies. It would be wonderful to see significant innovations in this area, such as enhanced support for AOP-based business interception, better stateful bean capabilities, and deeper integration with modern orchestration environments like Kubernetes.
Thank you

[hantsy]

Jakarta EE plans to replace EJB with pure CDI; I've seen several issues related to this. Yeah, I also thought EJB is still important to developers; some concepts in EJB, such as Stateful beans and manual persistence synchronization, have no replacements in CDI. More importantly, the Message-Driven Bean modernization was discussed 10 years ago and create CDI-compatible message listener, but it hasn't moved forward. A compromised solution is to make EJB itself more compatible with CDI, such as by accepting CDI transactional, etc. Like the project provided by OmniFish, https://github.com/OmniFish-EE/omni-beans

…

--- Regards, *Hantsy Bai* Self-employed consultant, fullstack developer, agile coach, freelancer/remote worker GitHub: https://github.com/hantsy Twitter: ***@***.*** Medium: ***@***.***

On Fri, May 22, 2026 at 11:32 AM lairoea-web ***@***.***> wrote: *lairoea-web* left a comment (jakartaee/platform#1285) <#1285 (comment)> I personally find EJB quite appealing and elegant. It was a visionary concept originally introduced by Sun Microsystems. In my view, enterprise-level Java EE applications have always relied heavily on EJB. I believe that future versions of Jakarta EE should not marginalize EJB. It remains the very soul of the Jakarta EE platform. If EJB were to be sidelined, Jakarta EE would lose much of what distinguishes it from frameworks like Spring. After all, true enterprise solutions are meant to be robust and comprehensive — and that’s precisely where EJB’s charm lies. It would be wonderful to see significant innovations in this area, such as enhanced support for AOP-based business interception, better stateful bean capabilities, and deeper integration with modern orchestration environments like Kubernetes. Thank you — Reply to this email directly, view it on GitHub <#1285 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGQT6D7ELXHVDT3AAPE62L437C3ZAVCNFSM6AAAAACZFI2PJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMJUG42DSNZZGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[scottmarlow]

CC jakartaee/enterprise-beans#165

[lairoea-web]

"I think EJB is very important for enterprise-level development. The heavyweight nature of EJB exists for a reason — being heavyweight means it comes with strong standardization, and I think that's perfect. If EJB gets marginalized, then what's the difference between it and the Spring framework? I think the fragmentation caused by microservices is not good. It's very hard to keep everything under control."