[
https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys...
]
Mark Struberg commented on CDI-50:
----------------------------------
This goes in the same direction as CODIs @ProjectStageActivated and @PropertyActivated -
it's just the other way around.
We have a n-staged lookup mechanism. You can either set the values via
* export MyProperty=myValue
* java .. -DMyProperty=myValue
* use a <context-param> in your web.xml
* use a JNDI value under java:/comp/env/myfaces-codi/MyProperty
depending on which environment is available (no JNDI -> no JNDI lookup; no servlet
-> no context-param lookup, etc)
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
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira