Message Title

[~juan.hernandez], what exactly do you want me to do to reproduce the problem. Your setup contains a bunch of domain classes and create a jar file with an empty beans.xml. I deploy this jar via the jboss command line client and get:

21:27:15,018 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "hv-861-1.0-SNAPSHOT.jar" (runtime-name: "hv-861-1.0-SNAPSHOT.jar")
21:27:15,859 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment hv-861-1.0-SNAPSHOT.jar
21:27:16,355 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.1.3.Final
21:27:16,859 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016005: Starting Services for CDI deployment: hv-861-1.0-SNAPSHOT.jar
21:27:17,148 INFO  [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.2.6 (Final)
21:27:17,321 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016008: Starting weld service for deployment hv-861-1.0-SNAPSHOT.jar
21:27:20,193 INFO  [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "hv-861-1.0-SNAPSHOT.jar" (runtime-name : "hv-861-1.0-SNAPSHOT.jar")

According to your description I would have expected this to throw an exception. I am also a bit surprised that your code does not contain any actual Bean Validation constraints. There is a @Valid on a string property, but that is not a constraint and in the context of Bean Validation does not even make sense, since @Valid is used to trigger cascaded validation for object graphs which does not really apply to a "simple" string.

Are you sure this is what I need to reproduce the problem? It would be great if you could double check your attached tarball and provide some detailed instructions on how to reproduce the error. Last but not least, I am using Wildfly 8.2.0.Final "Tweek"