Support @Any delegate injection points being able to automatically inject the bean being decorated, not doing a general lookup
------------------------------------------------------------------------------------------------------------------------------
Key: WBRI-341
URL: https://jira.jboss.org/jira/browse/WBRI-341
Project: Web Beans
Issue Type: Bug
Components: Interceptors and Decorators
Reporter: Pete Muir
Fix For: 1.0.0.CR2
Currently we treat delegate injection points like a normal injection point, meaning that if multiple beans will resolve to the delegate injection point, we fail at runtime. This seems incorrect to me - we should relax this restriction, even though the spec makes no requirements in this area.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Spec calls for any instance which has an IP with InjectionPoint to cause a Definition problem, but this seems very costly
-------------------------------------------------------------------------------------------------------------------------
Key: WBRI-308
URL: https://jira.jboss.org/jira/browse/WBRI-308
Project: Web Beans
Issue Type: Bug
Reporter: Pete Muir
Fix For: 1.0.0.CR1
org.jboss.jsr299.tck.tests.lookup.injectionpoint.broken.not.bean.InjectionPointOnNonBeanTest.test()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Move InterceptorBindingType to a 299-defined package
----------------------------------------------------
Key: WBRI-294
URL: https://jira.jboss.org/jira/browse/WBRI-294
Project: Web Beans
Issue Type: Bug
Components: Glassfish integration, Interceptors and Decorators
Affects Versions: 1.0.0.PREVIEW1
Reporter: Ken Saks
The original 299 implementation defined InterceptorBindingType within the javax.interceptor package. All 299 dependencies need to be removed from the javax.interceptor API so InterceptorBindingType should be moved to a 299-defined package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Calling BeanManager.validate(InjectionPoint) for an InjectionPoint belonging to a non-contextual bean results in NPEs
---------------------------------------------------------------------------------------------------------------------
Key: WBRI-354
URL: https://jira.jboss.org/jira/browse/WBRI-354
Project: Web Beans
Issue Type: Bug
Reporter: Kabir Khan
Fix For: 1.0.0.CR1
Attachments: patch.txt
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
NPE in SimpleInjectionTarget if no @PostConstruct/@PreDestroy methods
---------------------------------------------------------------------
Key: WBRI-351
URL: https://jira.jboss.org/jira/browse/WBRI-351
Project: Web Beans
Issue Type: Bug
Reporter: Kabir Khan
Fix For: 1.0.0.CR1
Attachments: patch.zip
Zip contains fix and test
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Same decorator class listed more than once in beans.xml does not throw deployment exception
-------------------------------------------------------------------------------------------
Key: WBRI-343
URL: https://jira.jboss.org/jira/browse/WBRI-343
Project: Web Beans
Issue Type: Bug
Components: Bootstrap
Reporter: Shane Bryzak
Fix For: 1.0.0.CR1
Assertion 8.2.bc states:
"If the same class is listed twice under the <decorators> element, the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container"."
The RI is not detecting this invalid configuration as a deployment problem - please refer to the following TCK test class (which is currently marked ri-broken):
org.jboss.jsr299.tck.tests.decorators.definition.broken.decoratorListedTwiceInBeansXml.DecoratorListedTwiceInBeansXmlTest
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira