[
https://issues.jboss.org/browse/CDI-526?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-526:
----------------------------------
Maybe we should be more explicit that exclude filters (and possibly include filters) are
*only applied to the types found in a specific bean archive*. E.g. users might be tempted
to use include filters to "add" types from the classpath.
Include filters
---------------
Key: CDI-526
URL:
https://issues.jboss.org/browse/CDI-526
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Packaging and Deployment
Affects Versions: 1.2.Final
Reporter: Jozef Hartinger
CDI has support for exclude filters in the beans.xml where a certain part of a bean
archive (no matter whether "annotated" or "all" type) can be excluded
from CDI processing on a package level, e.g:
{code:XML}
<exclude name="com.acme.rest.*" />
{code}
With the rise of fat jars and CDI support for SE it would also be useful to be able to
define an include filter. Suppose we have a single large jar file with all its
dependencies shaded in. This jar file has the beans.xml file which means that all the
packages in that file are processed (all classes are at least scanned for bean defining
annotations or even turned into CDI beans in "all" mode). We can obviously add a
couple of exclude filters for each of the libraries we do not want to scan. It would
however be much nicer if we could define a single include filter e.g.:
{code:XML}
<include name="my.application.*" />
{code}
Other packages (that belong to shaded-in libraries) in the same jar would not be scanned
at all.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)