[
https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys...
]
Mark Struberg reopened CDI-50:
------------------------------
Our preface still mentions @Requires. Plus it's not clear in 11.5.6 what happens if
there are package-info.java @Vetoed for the same package in different JARs.
Do we need to scan all jars for those first and merge the packages upfront? That could
slow down scanning.
It' also not clear from the Java Lang Spec what happens if you don't use
package-info.java but annotate the package in a single class file.
package-info.java is recommended, but the spec allows other ways as well:
http://docs.oracle.com/javase/specs/jls/se5.0/html/packages.html#7.4.1.1
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.PRD
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
For more information on JIRA, see:
http://www.atlassian.com/software/jira