Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [cdi-dev] Discussion: The new structure of EE integration sections

And yet the component spec project has no dependency in terms of CDI artifacts because the TCK tests are already in the platform TCK. It makes me question whether ratification of Persistence has been done correctly because to date we claim it is a wave 0 spec and can be ratified with the standalone TCK produced by the platform TCK team, and yet the specification describes integration requirements. It is just another example of inconsistent handling of integration requirements and dependencies. Move the integration requirements out of the Persistence spec and the problem is solved.

On Mon, Nov 20, 2023 at 5:55 AM Arjan Tijms via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:

On Mon, 20 Nov 2023 at 08:24, Ladislav Thon via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
 I agree it would be best if all specifications owned the CDI integration concerns, but as Scott mentioned, they don't want to,

In case of Jakarta Persistence, the CDI integration is already part of the spec. There's probably been a mistake in assumptions somewhere.

Kind regards,
Arjan Tijms

jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top