[
https://issues.jboss.org/browse/CDI-470?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-470:
----------------------------------
Yes, something like this sounds reasonable. Right now, you can only use exclude filters in
beans.xml or a portable extension and {{ProcessAnnotatedType.veto()}}. But it's not
that practical. What I'm trying to say is that it's not a perfect match to use an
annotation on a package to affect the subpackages.
Clarify @Vetoed on recursive package
------------------------------------
Key: CDI-470
URL:
https://issues.jboss.org/browse/CDI-470
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.2.Final
Reporter: Antonio Goncalves
It's not clear in the specification is {{@Vetoed}} only apply to the current package
or subpackages as well. This has been addressed on [CDI-299] but not solved. Either, we
make it clearer in the spec that it only addresses the current package and not
subpackages, or we could have a boolean, such as {{recursive}} :
{code:title=package-info.java}
@Vetoed(recursive=true)
package my.parent.package;
import javax.enterprise.inject.Vetoed;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)