[cdi-dev] exclude rules questions
mkouba at redhat.com
Mon Feb 3 04:49:29 EST 2014
Dne 31.1.2014 21:07, Mark Struberg napsal(a):
> A few questions regarding exclude rules
> 1.) does .* mean only the package, but no sub-packages. Whereas .** also includes sub-packages?
> Marek brought up another interesting note: com.foo.** would according to the wording also exclude com.foobar... Is that intended?
Yes, types from "com.foobar" would be excluded as well. I'm not sure it
was intended but we should not change the behaviour due to backwards
> 2.) Are multiple children allowed in an exclude rule in beans.xml?
Yep, check also the schema file (beans_1_1.xsd).
> There is a funny example in the spec:
> <exclude name="com.acme.ejb.**">
> <if-class-available name="javax.enterprise.inject.Model"/>
> <if-system-property name="exclude-ejbs"/>
> But I could not find the explanation what should happen. The if-class-available is nowhere stated. Or did I overlook it?
"if-class-available" is described above the example and in xsd. The
filter is active only if the classloader for the bean archive CAN
load a class for that name. So the filter will not be active if the
"Model" class can't be loaded or if the system property "exclude-ejbs"
is not set.
In any case the description of the example is not complete and we should
add a TCK test for this as well (AFAIK
org.jboss.cdi.tck.tests.deployment.exclude.ExcludeFiltersTest is not
testing multiple child elements).
> txs and LieGrue,
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
More information about the cdi-dev