The underlying service discovery issue manifests differently when an earlier version of bean validator is used which didn't use java.util.ServiceLoader:

javax.validation.ValidationException: Unable to get available provider resolvers.
	at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:259)
	at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:111)
	at com.sun.enterprise.v3.admin.CommandRunnerImpl.initBeanValidator(CommandRunnerImpl.java:459)
	at com.sun.enterprise.v3.admin.CommandRunnerImpl.checkAgainstBeanConstraints(CommandRunnerImpl.java:469)
	at com.sun.enterprise.v3.admin.CommandRunnerImpl.injectParameters(CommandRunnerImpl.java:441)
	Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassCastException: org.hibernate.validator.HibernateValidator cannot be cast to javax.validation.spi.ValidationProvider
	at javax.validation.Validation$DefaultValidationProviderResolver.getValidationProviders(Validation.java:332)
	at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:256)
	at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:111)
	at com.sun.enterprise.v3.admin.CommandRunnerImpl.initBeanValidator(CommandRunnerImpl.java:459)
	at com.sun.enterprise.v3.admin.CommandRunnerImpl.checkAgainstBeanConstraints(CommandRunnerImpl.java:469)
	Truncated. see log file for complete stacktrace

See ~~BVAL-280~~ for more details about how the earlier code looked like.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira