[cdi-dev] [JBoss JIRA] (CDI-50) Ability to veto beans, both unconditionally and based on classes visible

Mark Struberg (JIRA) jira-events at lists.jboss.org
Wed Jul 18 11:50:08 EDT 2012

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

Mark Struberg commented on CDI-50:

To be honest: I for one am not so fond about @Veto and @Requires yet ...

@Veto: completely underspecified!
* How can it be modified via Extensions?
* In which phase does it get applied? Directly at startup? Or only after ProcessAnnotatedType?
* all corner cases and exceptional behaviour, e.g. how does it fit together with @New?

@Requires: not user friendly
* against JSR-250
* adds tons of NoClassDefFound pitfalls
* how to prevent @Requires("wrongString") 

People should rather modularize their apps a bit better.
> Ability to veto beans, both unconditionally and based on classes visible
> ------------------------------------------------------------------------
>                 Key: CDI-50
>                 URL: https://issues.jboss.org/browse/CDI-50
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Concepts, Packaging and Deployment
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>            Assignee: Pete Muir
>             Fix For: 1.1.EDR2
> This should support both a straight veto, and conditional based on classes available.
> Seam Solder supports this as @Veto and @Requires({Foo.class, Bar.class}).
> Mark Struberg proposed using @Optional

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


More information about the cdi-dev mailing list