[
http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com....
]
Emmanuel Bernard commented on HV-24:
------------------------------------
Sounds to me that your Exception Handling mechanism (being a dev screen on the log system
in prod) should process Exceptions by type accordingly, ie if it's an
InvalidStateException, display the informations you want.
I am concerned about providing a flat version of the sub invalidValues in the Root
exception message: it's not really readable, and everybody want different
informations.
Improve the default message of InvalidStateException
----------------------------------------------------
Key: HV-24
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-24
Project: Hibernate Validator
Issue Type: Improvement
Components: engine
Affects Versions: 3.0.0.ga
Environment: Any
Reporter: Mike Quilleash
Doing a printStackTrace on InvalidStateException does not give the actual invalid values
anywhere. Would greatly improving debugging speed if this was included by default as
often this indicates a programming error. Currently I have to run the code again and
debug the right place to find out what the InvalidValues are.
--
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