Originally in CDI-1.0 it was REQUIRED to fail at boot time!
Not really. See below.
The CDI-1.0 TCK did REQUIRE to fail at boot!
Yes, it was a bug in TCK. Reported as CDITCK-263 and fixed in TCK 1.1.
The current version of the test is just pinning down Weld specific behaviour and even contradicts JSR-299!
What, why? CDI 1.0 wording is: "If an injection point whose declared type cannot be proxied by the container resolves to a bean with a normal scope, the container automatically detects the problem and treats it as a deployment problem." See also http://docs.jboss.org/cdi/spec/1.0/html/injectionelresolution.html#unproxyable. 6.5.3. Contextual reference for a bean is the same as well.
You will see that it will blow up...
Yes, the fix was not backported. See also https://issues.jboss.org/browse/WELD-1052?focusedCommentId=12709637&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12709637 |