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
Need more granular control of web beans discovery vs. sending of various initialization events
-----------------------------------------------------------------------------------------------
Key: WBRI-332
URL: https://jira.jboss.org/jira/browse/WBRI-332
Project: Web Beans
Issue Type: Bug
Components: Bootstrap, Events, Glassfish integration
Environment: 1.0.0.PREVIEW2.SP2 in GlassFish V3 trunk
Reporter: Ken Saks
In the current SPI, WebBeansBootstrap().bootstrap() performs web beans discovery and sends out any BeforeBeanDiscovery, AfterBeanDiscovery, and AfterDeploymentValidation events. We need more granular control of these individual actions to match the deployment phases in GlassFish. Other non-299 related initialization tasks need to take place after web beans discovery, so most important is to decouple the sending of the AfterDeploymentValidation event so it can occur after the EE application has made it through all initialization stages.
--
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
Support Just-In-Time Binding
----------------------------
Key: WBRI-280
URL: https://jira.jboss.org/jira/browse/WBRI-280
Project: Web Beans
Issue Type: Feature Request
Components: Simple Beans
Affects Versions: 1.0.0.PREVIEW1
Reporter: Takeshi Kondo
Assignee: Nicklas Karlsson
In guice , If a type is needed but there isn't an explicit binding, the injector will attempt to create a Just-In-Time binding.(http://code.google.com/p/google-guice/wiki/JustInTimeBindings)
However, If a type is needed but there isn't an explicit binding, WebBeans's BeanManager throws UnsatisfiedResolutionException.
If a type is concret class, BeanManager can create and inject a instance.
I want to use injection as instance creation. because of keeping simplicity of code.
Writing beans.xml is laborious.
for instance
--------
@ApplicationScoped
public class Counter{
@Current
java.util.concurrent.atomic.AtomicInteger atomicInteger;
...
-------
--
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
Validate that a bean name of the form x.y, where x is a another bean's name, is not allowed
-------------------------------------------------------------------------------------------
Key: WBRI-305
URL: https://jira.jboss.org/jira/browse/WBRI-305
Project: Web Beans
Issue Type: Bug
Components: EL integration
Reporter: Pete Muir
Fix For: 1.0.0.CR1
org.jboss.jsr299.tck.tests.lookup.byname.duplicatePrefixResolution.DuplicateNamePrefixResolutionTest.testDuplicateBeanNamePrefix()
--
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
InjectionPoint.getAnnotated is returning the wrong subclasses
-------------------------------------------------------------
Key: WBRI-309
URL: https://jira.jboss.org/jira/browse/WBRI-309
Project: Web Beans
Issue Type: Bug
Reporter: Pete Muir
Fix For: 1.0.0.CR1
org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest.testGetAnnotatedParameter()
org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest.testGetAnnotatedField()
--
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
Validate uniqueness of EL names within a the transitive closure of bean modules
-------------------------------------------------------------------------------
Key: WBRI-304
URL: https://jira.jboss.org/jira/browse/WBRI-304
Project: Web Beans
Issue Type: Bug
Components: EL integration
Reporter: Pete Muir
Fix For: 1.0.0.CR1
org.jboss.jsr299.tck.tests.lookup.byname.duplicateNameResolution.DuplicateNameResolutionTest.testDuplicateNamedBeans()
--
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