Document configuring and exposing a ValidatorFactory not just a Validator [SPR-6609]

[spring-projects-issues]

Mike Youngstrom opened SPR-6609 and commented

Sometimes a ValidatorFactory is required by thirdparty libraries such as JPA 2.0 with the "javax.persistence.validation.factory" property. It would be nice if it were possible to configure a single ValidatorFactory that can be passed to JPA 2.0 and LocalValidatorFactoryBean to help provide a more consistent validation configuration across an application's configuration.

This could simply be a bean similar to LocalValidatorFactoryBean but instead of providing a Validator it provided a ValidatorFactory.

Then modifying LocalValidatorFactoryBean or creating a new bean based on SpringValidatorAdapter that accepts a ValidatorFactory.

---

Affects: 3.0 GA

Referenced from: commits a70bb40

[spring-projects-issues]

Juergen Hoeller commented

Actually, LocalValidatorFactoryBean exposes both Validator and ValidatorFactory as client interfaces, delegating all calls to the underlying ValidatorFactory. Did you try simply passing the LocalValidatorFactoryBean reference into JPA 2.0 there?

Juergen

[spring-projects-issues]

Mike Youngstrom commented

You are correct. My bad. That should work fine for me. You might want to mention that feature in the documentation.

Perhaps under

http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/validation.html#validation-beanvalidation-spring-inject

javax.validation.Validator, org.springframework.validation.Validator, and javax.validation.ValidatorFactory

Feel free to close this or optionally change it to a documentation issue.

Thanks