[
https://issues.jboss.org/browse/CDI-470?page=com.atlassian.jira.plugin.sy...
]
Antonio Goncalves commented on CDI-470:
---------------------------------------
Hum... not that clear to me, but well.
Shall it stay like that ? I tend to add a package-level {{@Veto}} on my entities
({{org.mystuff.model}})... but in big projects my model is usually spllitted into sub
packages ({{org.mystuff.model.customer}}, {{org.mystuff.model.order}}, ...). Recursive
veto would be interesting.
Any thoughts ?
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)