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

In today's platform call it was pointed out that the JESP still refers to version 1.2 of the EFSP, which requires at least one compatible implementation implement all aspects including the optional elements:

We had added the removal of these optional technologies to the EE 10 project plan so that both Open Liberty and WildFly could be used for ratification of the web profile and platform specification. It is good that they are already marked as optional have flags that can disable them so that removal requires no work in the platform TCK. 

On Jun 14, 2022 at 4:07:32 PM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

On Tue, Jun 14, 2022 at 10:31 PM Tracy Burroughs <tkb@xxxxxxxxxx> wrote:
The question becomes, what advantage is there to remove these optional features from the Jakarta EE 10 Platform specification if the APIs still exist in the platform?  There is already no requirement for any vendor to implement them. 

There is however a requirement for them to be tested by at least one implementation for the ratification of the Jakarta EE 10 specification. Once removed that requirement would no longer hold, and we can propose e.g. WildFly as the compatible implementation to ratify Jakarta EE 10.

Kind regards,
Arjan Tijms
jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top