|Re: [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements|
Does this mean the Platform TCK would need to be updated to remove the use
of “EJB Entity beans” and the “Embeddable EJB Container”?
Tracy Burroughs (tkb@xxxxxxxxxx)
WebSphere Application Server Development
IBM Rochester, Dept AAW, Bldg H315/050-2
2800 37th Street NW, Rochester MN 55901-4441
We had targeted removal of the EJB features in the EE10 release plan: https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee10/JakartaEE10ReleasePlan For the Platform specification, the following two features will be tagged as “removed”
We had targeted removal of the EJB features in the EE10 release plan:
The removal of these technologies has been added to the current ManagedBeans deprecation PR:
The EFSP was targeting removing any language around optional features as described in these issues:
And this was incorporated into the EFSP 1.3(Version 1.3. Effective November 1, 2021), which no longer refers to optional behaviors:
Are we just needing to update the EE WG to adopt this?
Back to the top