Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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”?

I believe the Platform TCK contains some tests that have been made optional because they contain EJB Entity beans, despite also covering other aspects of EJB that are not optional.  I think the effort to separate them was considered too great to make it worthwhile.  If the EJB Entity aspects could just be completely removed, then what remains would no longer need to be optional.

This seems good for the platform but does have the side effect that there will no longer be any tests for these optional parts of the EJB specification, since the EJB specification does not have a separate TCK.  If the EJB specification and API could be updated for Jakarta EE 11 to also remove these optional features, then the problem will be short lived.

Tracy Burroughs  (tkb@xxxxxxxxxx)

WebSphere Application Server Development

IBM Rochester, Dept AAW, Bldg H315/050-2

2800 37th Street NW, Rochester MN 55901-4441

 

From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Stark
Sent: Tuesday, June 14, 2022 11:39 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements

 

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:

For the Platform specification, the following two features will be tagged as “removed” or “deprecated” (exact term and/or mechanism still needs to be determined).

  • EJB Entity Beans (CMP and BMP)
  • Embeddable EJB Container

 

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