Convert persistence storage exception into Bean Validation exceptions --------------------------------------------------------------------- Key: BVAL-213 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-213 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard This is not a problematic of Bean Validation per se but one of the issue people are facing is inconsistency in constraint reporting. For example, the database can raise a some kind of unique constraint exception (specific to each vendor usually). It would be ideal to get it converted into a @Unique constraint exception as defined by Bean Validation. Said differently by Christian {code}I'd rather see improvement of message propagation/mapping when an integrity rule inside the database has been violated. Like, turning a fatal database transaction exception (JDBCException wrapped etc.) into a clean error message, with a strong and stable mapping across DBMS products. If a UNIQUE constraint has been violated at the database level, I'd like to catch it and turn it into a Bean Validation error for my client. We have discussed this >5 years ago and at that time there was just no way to really guarantee that a JDBCException can tell you what the real cause of the problem was. Nobody standardized or required that the catalog name of the violated constraint is included so you couldn't map it. Maybe that's possible now. If not, at least the generic ConstraintViolationException should be an SPI of Bean Validation that JPA providers can throw.{code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira