[cdi-dev] [JBoss JIRA] Updated: (CDI-128) Ability to access CDI enhanced metadata from the InvocationContext.getMethod()

[Pete Muir (JIRA)]

     [ https://issues.jboss.org/browse/CDI-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated CDI-128:
--------------------------

        Fix Version/s: TBD
    Affects Version/s: 1.0


> Ability to access CDI enhanced metadata from the InvocationContext.getMethod()
> ------------------------------------------------------------------------------
>
>                 Key: CDI-128
>                 URL: https://issues.jboss.org/browse/CDI-128
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>    Affects Versions: 1.0
>            Reporter: Richard Hightower
>             Fix For: TBD
>
>
> The issues with InvocationContext is it was designed before CDI as part of EJB 3. In CDI, the meta-data will likely exist in an annotation, but it could exist in an XML file (Candi, and Seam XML Extension for CDI). 
> For example, I am working on creating a standard interceptor for JCache 107. I can read the annotation from the getMethod of the InvocationContext, but if someone added the interception meta-data in an XML file, then it will not be available to InvocationContext.getMethod().getAnnotation(Cacheable.class). 
> I propose we have an extension interface that extends InvocationContext called CDIInvocationContext that has a getAnnotated. This way if someone annotates in an XML file, then it is available to implementors for interceptors.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira