[
https://hibernate.onjira.com/browse/BVAL-264?page=com.atlassian.jira.plug...
]
Hardy Ferentschik edited comment on BVAL-264 at 2/8/12 11:29 AM:
-----------------------------------------------------------------
Right, but this is not something we can address in Hibernate Validator, but needs to be
done in Bean Validation. _ConstraintViolationException_ is a class from the BV api/spec.
Moving it to BVAL.
was (Author: hardy.ferentschik):
Right, but this is not something we can address in Hibernate Validator, but needs to
be done in Bean Validation. _ConstraintViolationException_ is a class from the BV
api/spec
Improve toString() in ConstraintViolationException
--------------------------------------------------
Key: BVAL-264
URL:
https://hibernate.onjira.com/browse/BVAL-264
Project: Bean Validation
Issue Type: Improvement
Environment: N/A
Reporter: David J. M. Karlsen
Labels: exception, toString
It would be nice if the mesage from ConstraintViolationException was better so that when
logging it would show the beanpath and errors by default.
Today it will just read:
{noformat}
javax.validation.ConstraintViolationException: null
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira