From f434944310c53d27ec169ef44857747067a55305 Mon Sep 17 00:00:00 2001 From: starksm64 Date: Mon, 12 Feb 2024 12:32:42 -0600 Subject: [PATCH] Add a section on the the Unified EL integration API Signed-off-by: Scott M Stark --- spec/src/main/asciidoc/core/spi_full.asciidoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/spec/src/main/asciidoc/core/spi_full.asciidoc b/spec/src/main/asciidoc/core/spi_full.asciidoc index 6acc6406..b573d5e2 100644 --- a/spec/src/main/asciidoc/core/spi_full.asciidoc +++ b/spec/src/main/asciidoc/core/spi_full.asciidoc @@ -560,6 +560,13 @@ In addition to rules defined in <>, the following rules appl The returned `Instance` object can only access instances of beans that are available for injection in the module or library containing the class into which the `BeanManager` was injected or the Jakarta EE component from whose JNDI environment namespace the `BeanManager` was obtained, according to the rules defined in <>. +[[el_support]] +=== Unified EL integration API + +Since CDI version 4.1, the Unified EL integration API, which is part of the `BeanManager` API, is deprecated. +The relevant methods are placed in a new interface `jakarta.enterprise.inject.spi.el.ELAwareBeanManager`, which is present in a new supplemental CDI API artifact: `jakarta.enterprise:jakarta.enterprise.cdi-el-api`. + +The requirements for supporting the Unified EL integration API are defined in the Jakarta EE Platform specification. [[alternative_metadata_sources]] === Alternative metadata sources