[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-232:
------------------------------------------
Ok got it. I read it in the wrong way. So 5.6.2 should become something like:
{quote}
The container must provide a built-in bean with:
* Instance<?> and Provider<?> in its set of bean types,
* scope @Dependent,
* no bean name, and
* an implementation provided automatically by the container.
*For all injection point of type Instance<T> or Provider<T> the container must
validate that at least one bean with T in its set of bean types exists. If such a bean
doesn't exist, the container automatically detects the problem and treats it as a
deployment problem*
The built-in implementation must be a passivation capable dependency, as defined in
Passivation capable dependencies.
{quote}
We probably should also mention qualifiers in the validation sentence.
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL:
https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)