]
Antoine Sabot-Durand updated CDI-500:
-------------------------------------
Sprint: Sprint 1
Clarify @Intercepted Bean metadata injection for EE components
--------------------------------------------------------------
Key: CDI-500
URL:
https://issues.jboss.org/browse/CDI-500
Project: CDI Specification Issues
Issue Type: Clarification
Components: Interceptors
Affects Versions: 1.2.Final
Reporter: Martin Kouba
Fix For: 2.0 .Final
It's not clear what should happen when an interceptor with {{@Intercepted Bean}}
metadata is associated with an EE component.
See the CDI spec, "5.5.8. Bean metadata":
{quote}
Additionally, the container must provide beans allowing interceptors and decorators to
obtain information about the beans they intercept and decorate:
* a bean with scope @Dependent, qualifier @Intercepted and type Bean which can be
injected into any interceptor instance, and
* ...
{quote}
However, most EE components must also support the use of CDI interceptors. See also the
Java EE 7 spec, "EE.5.2.5 Annotations and Injection":
{quote}
The component classes listed in Table EE.5-1 with support level "Standard"
all support Java EE resource injection, as well as PostConstruct and PreDestroy
callbacks. In addition, if CDI is enabled—which it is by default—these classes also
support CDI injection, as described in Section EE.5.24, "Support for Dependency
Injection", and the use of interceptors.
{quote}