[cdi-dev] [JBoss JIRA] (CDI-216) @Veto and ProcessAnnotatedType

Pete Muir (JIRA) jira-events at lists.jboss.org
Wed Aug 29 12:22:32 EDT 2012

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

Pete Muir resolved CDI-216.

    Fix Version/s:     (was: 1.1 (Proposed))
       Resolution: Duplicate Issue

I'm closing this as a dupe, as the discussion is happening on CDI-50
> @Veto and ProcessAnnotatedType
> ------------------------------
>                 Key: CDI-216
>                 URL: https://issues.jboss.org/browse/CDI-216
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Concepts, Packaging and Deployment
>    Affects Versions: 1.1.EDR
>            Reporter: Gerhard Petracek
>            Assignee: Mark Struberg
>            Priority: Critical
> currently the spec. specifies:
> "The container must fire an event for each Java class or interface it discovers in a bean archive, and for annotated type added by BeforeBeanDiscovery.addAnnotatedType(), before it reads the declared annotations."
> that's ok for cdi 1.0.
> however, if @Veto gets added to cdi 1.1, we need a clarification here.
> the internal implementation via a std. cdi doesn't make sense because other extensions still get the corresponding ProcessAnnotatedType event.
> -> Annotated types with @Veto (or as suggested at CDI-50: @Unmanaged or @Exclude) shouldn't lead to a ProcessAnnotatedType event.

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

More information about the cdi-dev mailing list