Hello,

I'm using the bean validation API and its implementation provided by Hibernate validator for the first time.

I've setup my project using maven. I've put the following dependencies amongst others:

<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
<version>3.1.0.GA</version>
</dependency>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
</dependency>

Then I annotated one of my classes with the JSR 303 annotations, created an instance of it and tried to validate it. But the following method failed:



The exact exception is:



After reading some forums I understood that a JSR 303 implementation should be in my classpath. I have it - hibernate-validator. Next I did some debugging and found that my hibernate-validator jar is missing META-INF/services/javax.validation.spi.ValidationProvider file and thus the validator resolver cannot find which is the exact implementation to instantiate.

Could you help me with this? It seems that it's only me in the whole internet, that has this problem, so apparently I'm doing something wrong. :-)

Thanks,
Ivan

Hello,
hibernate-validator 3.1 is the precursor of the standard, to use the new javax.validation API you need to use version 4:

Hello s.grinovero,

Thank you very much. I changed the hibernate-validator version and it worked well.

Funny enough, I'm using the m2eclipse plugin, which provides something like code completion for most of the dependency attributes, including the version. So, according to my eclipse distribution, the latest version was 3.1.0, that is why I chose that.

Anyway, thanks for the quick and correct reply!

BTW, I did not have to specify the javax.validation dependency explicitly. Probably hibernate-validator has it in its pom.xml.

Regards,
Ivan

just remember the m2eclipse plugin is indexing only the artifacts you have used before, or for which it was able to download a compressed index. Most repositories don't provide such an index, so your local index will not reveal new release until you use them explicitly..