[cdi-dev] [JBoss JIRA] (CDI-132) Clarify which initial info AnnotatedType should contain

[Mark Struberg (JIRA)]

    [ https://issues.jboss.org/browse/CDI-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713901#comment-12713901 ] 

Mark Struberg commented on CDI-132:
-----------------------------------

yikes, disposal methods can be static :/
So all is fine and we also need static methods/fields in the AnnotatedType
                
> Clarify which initial info AnnotatedType should contain
> -------------------------------------------------------
>
>                 Key: CDI-132
>                 URL: https://issues.jboss.org/browse/CDI-132
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Portable Extensions
>            Reporter: Mark Struberg
>            Assignee: Pete Muir
>            Priority: Minor
>             Fix For: 1.1.EDR
>
>
> The spec is not exactly clear about the initial content of AnnotatedType.
> When initially building the AnnotatedType (e.g. before handing it over to the Extensions) we need to pre-fill them with the info from the annotations from the classes.
> Should this AnnotatedType:
> 1.) contain no annotations from superclasses?
> 2.) contain all annotations from superclasses?
> 3.) contain @Inherited annotations from superclasses?
> I think the other questions already got cleared up in CDI-70:
> Should AnnotatedType contain derived public? protected? private? methods/fields from a superclass?
> Imo it should contain all information which would be available by manually parsing any annotations. In other words: it should be possible to completely modify or emulate annotations of a parsed type.

--
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