Home/ Questions/Q 6190831
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T02:39:31+00:00

I added some validation ( @NotNull ) to managed beans and suddenly got this

  • 0

I added some validation (@NotNull) to managed beans and suddenly got this error. Any ideas what might cause it? The application runs in Apache Tomcat 7.

javax.validation.ValidationException: Unable to find a default provider
javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264)
javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:111)
javax.faces.validator.BeanValidator.validate(BeanValidator.java:271)
javax.faces.component.UIInput.validateValue(UIInput.java:1127)
javax.faces.component.UIInput.validate(UIInput.java:941)
javax.faces.component.UIInput.executeValidate(UIInput.java:1189)
javax.faces.component.UIInput.processValidators(UIInput.java:691)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1080)
javax.faces.component.UIForm.processValidators(UIForm.java:243)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1080)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1080)
javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1180)
com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It appears that there is no JSR 303 Bean Validation provider in the classpath of your application in the application server. If you are using Glassfish, it would be better if you can verify the presence of bean-validator.jar in the $GLASSFISH_INSTALL_ROOT/glassfish/modules directory; Glassfish 3.1 uses this JAR (which contains the Hibernate Validator implementation) to serve as the default JSR 303 Bean Validation provider. I suspect that you are using an older version of Glassfish, or another application server that does not contain a Bean Validation provider.

    If you must include a Bean Validation provider in the classpath, consider reading the Java API documentation for the ValidationProviderResolver interface, which states that:

    Bean Validation providers are identified by the presence of
    META-INF/services/javax.validation.spi.ValidationProvider files
    following the Service Provider pattern described here

    Each META-INF/services/javax.validation.spi.ValidationProvider file
    contains the list of ValidationProvider implementations each of them
    representing a provider.

    Therefore, if you do include a Bean Validation provider in your classpath manually, you must ensure the presence of the META-INF/services/javax.validation.spi.ValidationProvider file in the classpath, and also that it contains the name of the Bean Validation provider. The contents of one provided by Glassfish is listed below, and points to the Hibernate Bean Validator class:

    org.hibernate.validator.HibernateValidator
    • 0