[
https://issues.jboss.org/browse/CDI-70?page=com.atlassian.jira.plugin.sys...
]
Arne Limburg commented on CDI-70:
---------------------------------
OK, but then the complete section should be more concrete. What about fields from
superclasses, especially when a field of the same name exists in the subclass. I would
expect that AnnotatedType.getFields() returns both, whereas I would expect that overridden
methods from a superclass are not contained in AnnotatedType.getMethods(). But none of
these things is currently specified.
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: Clarification
Components: Portable Extensions
Affects Versions: 1.0
Reporter: Pete Muir
Assignee: Pete Muir
Fix For: 1.1.EDR1
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. If the
parameters for a method or a constructor don't match the underlying class, it should
be considered a definition error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira