I have read the most recent documentation and I was curious how to tell Hibernate Validator to return the error on a field even though it is a class constraint. Take this for example:


I'd really love it if that @UniqueResumeSkill constraint could actually report as an error on the "skill" field/property. I really have no clue how to tell Hibernate Validator to do that. I thought other people may be curious how to do this too, as this is a pretty common problem that happens frequently.

The reason is that Spring really depends on bean property paths, and while with a bit of effort it is possible to dig for the class-level constraint in the Spring errors object, I'd rather just point it to the skill field/property. Semantically, that's really where the error is in this case. They need would need to select a different Skill from the drop down box, so it makes sense to put the error here than at the class/form level.

Does Hibernate Validator have this capability yet? Do you think it may in the future if it doesn't already? Any notable workarounds? :)

Thanks!

I looked into ConstraintValidatorContext and ConstraintValidatorContextImpl, but I don't see the obvious answer here. Most of these methods are getters, and the one buildBlah( string ) method returns an exception saying it's abstract ;)

Hi,

you probably want to do something like this in the validator once you figured out that the problem is in the skill field. Or course you can also provide a different message template:



Have a look at ConstraintValidatorContextTest (for example in fisheye)

--Hardy

I tried the following bit of code, but I get a compile-time error:



The error:


:(

perhaps it would be best to wrap this into a rerouteErrorToProperty() ;)

I am not sure why you have to cast to ConstraintValidatorContextImpl. The isValid method in the ConstraintValidator implementation gets passed an instance of ConstraintValidatorContext. Use the public API on this instance.

Have you seen the usage examples in fisheye?

--Hardy

The problem hardy is that these methods are not on the interface. My IDE says they are red. Could I possibly have an older copy of javax.validation while still having 4.0.0.ga of hibernate validator? I'm just letting maven do it's thing.

Regardless, casting should be safe here.. no? I don't plan on using another implementation other than Hibernate.

I'll look at the fisheye stuff. I just took your code and assumed it would be correct.

Well, I see that you're having an easier time compiling that group/persons example at the bottom of the file.

This is the error I get:



So it's not just my IDE... it's maven too :(

If I don't include the Impl, this is what I get:

Yay, I got it to work!

I added this to maven and it seems like it works:



Perhaps telling your maven dependencies in 4.0.0.ga to pull this specific version is in order?

Thanks Hardy

Hi again,

I think the problem lies somewhere on your side. Hibernate Validator 4.0.0.GA already has a transitive dependency to validation-api 1.0.0.GA (http://repository.jboss.com/maven2/org/ ... 0.0.GA.pom) You should not have to specify it explicitly.

Maybe you maven repo is corrupt. Might be worth just deleting your local repo and start from scratch.

Anyways, happy to hear that ConstraintValidatorContext works now for you :)

--Hardy