CHALLENGE:
Two test cases within the BeanValidation TCK suite:

1) org.hibernate.beanvalidation.tck.tests.xmlconfiguration.versioning.UnknownVersionInValidationXmlTest
2) org.hibernate.beanvalidation.tck.tests.xmlconfiguration.InvalidXmlConfigurationTest

Fail unexpectedly due to a deployment exception:

javax.enterprise.inject.spi.DeploymentException: Exception while deploying application.
Caused by: javax.enterprise.inject.spi.DeploymentException: Exception while checking application state.
Caused by: javax.enterprise.inject.spi.DeploymentException: Timeout while waiting for ApplicationState to reach STARTED

Both cases exercise the BeanValidation API and expect a ValidationException, because test application 1) declares an unsupported specification level within its BeanValidation configuration, and 2) provides an invalid (syntactically incorrect) BeanValidation configuration. The tests fail because the application server detects the faulty BeanValidation configurations and does not place into service the test applications that exercise the BeanValidation API.

The application server may encounter faulty BeanValidation configurations during application deployment – for example, while processing annotations of BeanValidation dependencies to be injected. When a server encounters a faulty configuration during deployment it is appropriate, or at least acceptable, that said server immediately indicates the causal ValidationException and does not place the improperly configured application into service. The Java Enterprise Edition specification does not require an application server to deploy nor serve requests upon an application containing an invalid BeanValidation configuration. These tests should be revised to pass regardless of whether the expected validationException occurs during application deployment or during service.

[Bean Validation configuration = validation.xml]