[cdi-dev] [JBoss JIRA] Updated: (CDI-62) Clarify @Resource/@PersistenceContext/etc. on disabled alternatives

[Pete Muir (JIRA)]

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

Pete Muir updated CDI-62:
-------------------------

    Fix Version/s: 1.1 (Proposed)
                       (was: TBD)


> 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
>          Components: Java EE integration
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>             Fix For: 1.1 (Proposed)
>
>
> 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