concerning "How is CDI BeanManager (or equivalent) injected into Bean
Validation?" I'm wondering whether we really require something like
Couldn't the CDI runtime just set a CDI-aware
ConstraintValidatorFactory when creating the Validator(Factory). We
then wouldn't have any dependency to CDI in BV at all. On the downside
this would mean CDI-enabled validators would only work when using a
validator managed by CDI but not using a validator retrieved via
Validation.buildDefaultValidatorFactory() but that would be ok IMO.
So generally I think the BV/CDI integration should be more
triggered/managed from the CDI side than the other way around.
2011/10/21 Emmanuel Bernard <emmanuel(a)hibernate.org>:
I've been thinking about BVAL-238 and came up with a first round of ideas and open
It is available here http://beanvalidation.org/proposals/BVAL-238/
Please give me your feedback. I think this issue can be closed quite quickly.
I've also created a proposals section on the website that will contain such work in
progress proposals before inclusion in the spec proper. Check out
On a side note, for casual website editing, you can use GitHub's `Edit this file`
It's not quite a wiki but that's pretty close. One thing you cannot do is create a
new file unfortunately. Anyone that have asked for write access should see this button.
beanvalidation-dev mailing list