Multiple 'org.springframework.validation.Validator' beans are exposed as of Spring Boot 1.5

[okohub]

Hello,

Looks like there are more than one org.springframework.validation.Validator type beans in context when using spring-boot-starter-web

First one is coming from: jsr303Validator, that is defined in
org.springframework.boot.autoconfigure.validation.ValidationAutoConfiguration

Second one is coming from: mvcValidator, that is defined in
org.springframework.boot.autoconfigure.web.WebMvcAutoConfiguration.EnableWebMvcConfiguration#mvcValidator

Thanks!

You can check test in sample project: https://github.com/okohub/validatorproblem

[snicoll]

Yes. How is that a problem? This was already the case in 1.5.0 by the way ...

The JSR303 validator exposes a standard javax.validation.Validator which is the type that you should inject. If you want the mvcValidator, just qualify it but behinds the scenes (in your project) this is the same bean.

There is nothing we can do as Spring MVC exposes a validator and we can't really disable that. If you do not want such validator to be bound automatically, exclude the ValidationAutoConfiguration. Another option is to add your own configurer, something like

@Configuration
public class MyMvcConfiguration extends WebMvcConfigurerAdapter {

    @Bean
    @Primary
    public Validator myValidator() {
      return new LocalValidatorFactoryBean();
    }   

    @Override
    public Validator getValidator() {
        return myValidator();
    }

}

[snicoll]

relates to #8481

[kappmeier]

We got the same when upgrading from 1.4 to 1.5. Validator has not been used before, so as a quick workaround we could solve this by setting

@EnableAutoConfiguration(exclude = {ValidationAutoConfiguration.class})

[snicoll]

I've considered various options and flagging the validator used in auto-configuration @Primary seems like the only option I have left.