The question from the linked issue might be better posed as “Are CDI EE implementors required to provide an implementation for the CDI SE interfaces, too?”
The CDI specification states: “CDI implementations that support the Java SE API are required to support CDI Full.” This implies (but does not outright state) that there can exist CDI implementations that do not support the Java SE API.
-Brian
From: cdi-dev <cdi-dev-bounces@xxxxxxxxxxx>
On Behalf Of Scott Marlow
Sent: Friday, June 3, 2022 12:17 PM
To: cdi-dev@xxxxxxxxxxx
Subject: [EXTERNAL] [cdi-dev] Why are CDI 4.0 Full implementations required to also provide SE (e.g. jakarta.enterprise.inject.se.SeContainer*) support?
Hi, Why are CDI 4.0 Full implementations required to also implement the CDI SE interfaces like jakarta.enterprise.inject.se.SeContainer*? This came up in discussion
on a JSON-B TCK challenge [1].
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Hi,
Why are CDI 4.0 Full implementations required to also implement the CDI SE interfaces like jakarta.enterprise.inject.se.SeContainer*? This came up in discussion on a JSON-B TCK challenge [1].
Thanks,
Scott
[1] https://github.com/eclipse-ee4j/jsonb-api/issues/326