Hardy Ferentschik, Gunnar Morling should we spin a Bean Validation API 1.0.1 to fix that one?

I guess this shouldn't take too much time, so we could do it. OTOH one can work around the issue by creating a custom provider resolver which basically looks like the one from WildFly and use it like this:

Validator validator = Validation
    .byDefaultProvider()
    .providerResolver( new MyCustomResolver() )
    .configure()
    .buildValidatorFactory()
    .getValidator();

Given this works as expected, I think there is no strict need for an update.

Btw. A. Mueller, you said you're using JBoss AS 7. How do you bootstrap your validator factory in this case? Normally you shouldn't be required to bootstrap one yourself via Validation but you can use the one provided by the container (via JNDI, @Inject, @Resource). As this one is bootstrapped internally using a custom provider resolver as well, the issue shouldn't show up in this case. Note that you can configure the validator factory retrieved that way via META-INF/validation.xml if required.