[
https://issues.jboss.org/browse/CDI-58?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on CDI-58:
------------------------------
We discussed this in a special EG meeting last week. The conclusion was
* allow multiple annotated types per class instance
* introduce an
{code}
public interface IdentifiedAnnotatedType<X> extends AnnotatedType<X> {
public String getId();
}
{code}
* if addAnnotatedType() is called, an existing AnnotatedType already exists in the bean
archive (either due to scanning, or due to a previous addAnnotatedType() operation) then
an instance of IdentifiedAnnotatedType must be passed, otherwise, a deployment exception
will occur.
* we will recommend extensions always add IdentifiedAnnotatedTypes so that they cannot
cause a deployment exception due to unexpected external circumstances.
Clarify that there can be multiple AnnotatedType instances per Java
class
-------------------------------------------------------------------------
Key: CDI-58
URL:
https://issues.jboss.org/browse/CDI-58
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans, Portable Extensions
Affects Versions: 1.0
Reporter: Pete Muir
Assignee: Pete Muir
Priority: Critical
Fix For: 1.1.PRD
This decision is really important to make. Either we remove/redefine
BeanManager#getAnnoatadType(Class) or we remove the 'artificial annotated types'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira