@sandy:
Check out this post: http://java.dzone.com/articles/using-hibernate-validator , under “Customizing Error Messages”.

No validator could be found for type: java.lang.Integer

I did nothing more than @Min(value = 5, message=”my message”)

It works nice just for @NotEmpty values!

What is worng?

“No validator could be found for type: java.lang.Long”

Is there any other info on this? Is there any workaround?

How was this resolved?

Thanks.

That should say “ValidationMessages.properties”, with an “s” before the dot.

Anyway, I tried creating a little test to test this whole thing out using Spring MVC (3.0) and Hibernate Validation (4.0.2). I created a simple form that captures a ‘name’ and an ‘ID’, which were backed by a form bean containing a String and a Long, respectively. I wired up a Spring controller using annotations (specifically, @Valid). The form displays correctly, and I intentionally enter data that violates the constraints. Now here’s where the problem comes in. When I submit the form, I get a 500 error and a long stacktrace with the following message: “javax.validation.UnexpectedTypeException: No validator could be found for type: java.lang.Long”. I tried replacing the wrapper Long with a primitive ‘long’ type, but the same exception gets thrown with the same error message. So my understanding now is that the new Bean Validation is not even able to understand primitive types except for ‘String’. That’s almost as bad as javac not understanding a ‘char’ or ‘byte’. If I turn on debug logging, I see that Spring itself is able to convert from the submitted form’s String to a Long. It’s the validator itself that doesn’t understand what a Long is (the validator fires after Spring has finished performing conversion, according to the call sequence indicated in the logs). Uri, can you confirm that this is true? Try doing this yourself by using a command/form-bean containing a Long (you don’t even need to put a constraint on it, in fact), and see if you can submit a form. I find it hard (or even impossible) to believe that it can’t understand even primitive types, so I’m assuming that there is some kind of disagreement between Spring and Hibernate Validator.
I’d appreciate it if you could test this out and see if you can duplicate this. If so, a bug report is in order.

Michael Chang

Please could you post your solution — I have a similar setup as you and I am looking for the same functionality. I have tried a number of things but at the moment just not working.

thanks