Re: [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers

[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

From: arjan tijms <arjan.tijms@xxxxxxxxx>
Date: Tue, 14 Jun 2022 22:13:50 +0200
Delivered-to: jakartaee-platform-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakartaee-platform-dev/>
List-help: <mailto:jakartaee-platform-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>, <mailto:jakartaee-platform-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakartaee-platform-dev>, <mailto:jakartaee-platform-dev-request@eclipse.org?subject=unsubscribe>

Hi,

On Tue, Jun 14, 2022 at 9:17 PM Tracy Burroughs <tkb@xxxxxxxxxx> wrote:

since the EJB specification does not have a separate TCK.

There is a separate TCK for EJB-Lite in the works, and maybe eventually that can lead to a separate TCK for all of EJB?

Kind regards,

Arjan Tijms

References:
- [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements
  - From: Scott Stark
- Re: [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements
  - From: Tracy Burroughs

Prev by Date: Re: [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements
Next by Date: Re: [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements
Previous by thread: Re: [jakartaee-platform-dev] EJB feature removal, EFSP no longer refers to optional requirements
Next by thread: [jakartaee-platform-dev] Platform apis restaged
Index(es):
- Date
- Thread

Back to the top