There seems to be a bug in the bean validator deployer filter config.
deployers/beanvalidation.deployer/META-INF/bv-core-jboss-beans.xml
When deploying a ear with a jar containing a beans.xml(CDI) this happens:
First the BeanValidator kicks in on the jar file, but not ear(due to filtering),
then WeldBoostrapDeployer kicks in on the Ear deployment.
The WeldBootstrapDeployer fails to start due to not finding the ValidatorFactory provided by the Bean Validator deployer..
The filer is defined as:
<set> <value>org.jboss.metadata.ear.spec.EarMetaData</value> <value>org.jboss.metadata.web.jboss.JBossWebMetaData</value> <value>org.jboss.metadata.ejb.jboss.JBossMetaData</value> </set>
<set> <value>org.jboss.metadata.ear.jboss.JBossAppMetaData</value> <value>org.jboss.metadata.web.jboss.JBossWebMetaData</value> <value>org.jboss.metadata.ejb.jboss.JBossMetaData</value> </set>
I fixed it in jsr303/deployers and I'm waiting for my AS/trunk to synch to fix it there as well.
* https://jira.jboss.org/jira/browse/JBAS-7486