I was getting a feel of Hibernate Validator http://www.hibernate.org/subprojects/validator.html and its integration with the JPA (also provided by Hibernate). I was expecting ConstraintValidationException to be thrown separately (so that it can be handled separately), but it seems that the exception is wrapped inside the PersistenceException. I am a little confused as to the reason for this behavior. Also, what would be the best way to handle the ConstraintViolationException and present the user with the customized messages. Here is the environment that I am using

Java Swing (J2SE 6)
Hibernate JPA (sub set of full Hibernate)
MYSQL database.

regards,
Nirvan.

Hi,

can you post your code? I don't think that the ConstraintValidationException should be wrapped. There is also a unit test in Hibernate which shows that a ConstraintValidationException is thrown directly - see here.

Regarding the handling - ConstraintValidationException contains a method called getConstraintViolations which you can use to access the actual validation errors. From the errors you get access to the validation error messages. How you are going to display them is up to you.

--Hardy