Clarify that if an extension provides an Annotated* then it is considered "metadata complete"
---------------------------------------------------------------------------------------------
Key: CDI-70
URL: https://issues.jboss.org/browse/CDI-70
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
I think the correct behavior is to ignore any members that are missing from the AnnotatedType. You should not be directly accessing the reflection API at all.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Clarify @Resource/@PersistenceContext/etc. on disabled alternatives
-------------------------------------------------------------------
Key: CDI-62
URL: https://issues.jboss.org/browse/CDI-62
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
Is it expected that the container validates these dependencies and fails deployment if they don't exist? I think it is, right? At least, I think some containers behave this way. Then we should say that this validation should *not* happen if the annotation appears in a class annotated @Alternative. I have no idea what the right language would be...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add section on cyclic dependencies to the spec
----------------------------------------------
Key: CDI-63
URL: https://issues.jboss.org/browse/CDI-63
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Pete Muir
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
In lifecycle chapter, clarify creation of interceptors/decorator
----------------------------------------------------------------
Key: CDI-60
URL: https://issues.jboss.org/browse/CDI-60
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Producers and beans that are under construction
-----------------------------------------------
Key: CDI-61
URL: https://issues.jboss.org/browse/CDI-61
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
I think we need the spec to say something about cases where an injection point of a bean resolves to a producer method of the same bean. The implementation should detect that this is a definition error. It shouldn't try to call a producer method on a non-fully-initialized bean.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Clarify that scope types should not have members
------------------------------------------------
Key: CDI-56
URL: https://issues.jboss.org/browse/CDI-56
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Pete Muir
The spec should mention that @ScopeType annotations should not have annotation members. Perhaps this should be a definition error. javax.inject.Scope already mentions this.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Clarify that not all classes in a bean archive are bean classes
---------------------------------------------------------------
Key: CDI-57
URL: https://issues.jboss.org/browse/CDI-57
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
We should be clearer and say that you can put non-bean classes (e.g.MDBs) in a bean archive.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Clarify that interceptors/decorators don't apply to producers in resolution rules
---------------------------------------------------------------------------------
Key: CDI-59
URL: https://issues.jboss.org/browse/CDI-59
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Bean declaration at constructor level
-------------------------------------
Key: CDI-55
URL: https://issues.jboss.org/browse/CDI-55
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Pete Muir
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean
---------------------------------------------------------------------------------------------------------------------------------------
Key: CDI-52
URL: https://issues.jboss.org/browse/CDI-52
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira