javax.validation.ValidationException: Unable to find default provider

I am currently working on Spring开发者_运维问答 MVC web app and trying to hook up validation using the @Valid annotation. When I fire up the application I'm getting the following exception:

javax.validation.ValidationException: Unable to find a default provider

I have Hibernate Validator 3.1.0.GA on the classpath as well as javax validation 1.0.0.GA, Hibernate Core 3.3.1.GA and Hibernate Annotations 3.4.0.GA.

Is there an incompatiblity in those versions that I'm not seeing, or can anyone think of any reason why I'm still getting this exception with Hibernate Validator on the class path?

Cheers,

Caps

See this answer : https://stackoverflow.com/a/3989936/325742

To fix, Add this maven dependency Hibernate Validator Annotation Processor.

<dependency>
  <groupId>org.hibernate</groupId>
  <artifactId>hibernate-validator-annotation-processor</artifactId>
  <version>4.1.0.Final</version>
</dependency>

That's the latest stable version of that artifact, as seen from here

Generic way of finding a dependency

Let's say that you got a a NoClassDefFoundError stating that the class org.postgresql.Driver was not found.

1. Use Jarvana to search for a dependency that can provide org.postgresql.Driver like so : http://www.jarvana.com/jarvana/search?search_type=class&java_class=org.postgresql.Driver which gives

   

2. Translate the above dependency into maven dependency format :

   <dependency>
       <groupId>postgresql</groupId>
      <artifactId>postgresql</artifactId>
      <version>9.1-901.jdbc4</version>
    </dependency>
   

3. Confirm that the above is available at Maven Central by searching like this :
   g:"postgresql" AND a:"postgresql"
   (where g stands for GroupID and a stands for artifactID)

4. Finally, add it to your pom.xml

Finding Dependencies using m2e

If you have an approximate idea of the dependency needed or can figure out the one you need given a list, then m2e's dependency search can be the quickest way of adding a dependency to your pom.xml

Steps :

1. Click on the Dependencies tab (A) in your pom.xml
2. Click on Add (B)
3. Search for the dependency by groupId/artifactId (C)
4. Double click the required one from the search results to have it added directly to your pom.xml (D)

A-D marked in the following snapshot :

Finding dependencies in IntelliJ Idea

In IntelliJ, looking up a dependency is much easier. All you need to do, is to make sure that the maven central repo has been indexed by IntelliJ like so:

And then, go into the pom, do a dep+Tab (or an Alt+Insert as shown here), and this is what you get:

If you are in a class which has an unresolved import, then the quick fix gives you an option of searching and adding the corresponding maven repo by doing an Alt+Enter on the missing Class/Package:

Awesome I say !

Hibernate Validator 3.1 is not a JSR303 provider. You need to upgrade to Hibernate Validator 4 or later.

This happened to me without Hibernate.

Running great on my PC, it didn't work on my EC2 Linux server.

The reason was an existence of validation-api-1.0.0.GA.jar file under /usr/share/tomcat/lib.

Once validation-api-1.0.0.GA.jar deleted, it worked great.

In my case, I had the same problem, but it was happening because the jar of hibernate-core version 4.1.8.Final downloaded by maven was corrupted. I swithed to version 4.1.6.Final and it started working. I was using STS and spring repositories.

Hope this helps someone.

In same Situation i update my Jar version only for anotations from hibernate-anotation and hibernate-common-annotation to Hibernate4 anotations which are listed below. For Hibernate 4 you can use this jars-

1-hibernate-commons-annotations-4.0.5.Final 2-hibernate-validator-4.2.0.Final

Hope this will work for you also.

I received the following error:

Invocation of init method failed; nested exception is javax.validation.ValidationException: Unable to get available provider resolvers

I discovered that in my WEB-INF/lib directory I had two versions of Validator.class present in both of the following jar files:

• org.springframework.context-3.1.1.RELEASE.jar
• com.springsource.javax.validation-1.0.0.GA.jar

I removed the com.springsource.javax.validation-1.0.0.GA.jar from the WEB-INF/lib directory because it is older and no longer supported. After doing so, my application worked perfectly. I learned from other posts that my problem had something to do with duplicate versions of the same file on the classpath. I figured out which file was causing the problem after reading Spring 3 Validation