Gunnar,
I surely will need some implementation of bean validation. I'm deploying on glassfish and websphere (7 and 8). Making hibernate validator scope provided would solve the problem nicely provided that that implementations is being used by the application server I'm running on. Can you confirm that if hibernate validator is included in the war it will be automatically registered as provider? It's a scenario I would prefer to avoid which is why I'm looking to separate those extra constraints which in principle are perfectly portable across different implementations. I just don't feel right about being forced to register hibernate validator as a provider because we are using those constraints. For me the point of the validation api is to have portable implementations of constraints regardless of the provider.
|