[hibernate-issues] [Hibernate-JIRA] Commented: (HV-24) Improve the default message of InvalidStateException
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Tue Oct 19 04:30:50 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38801#action_38801 ]
Emmanuel Bernard commented on HV-24:
------------------------------------
Right, we have improved things on the 4.x (non legacy) branch and thus people moving to HV 4 should not have the issue. I was talking more about people still using Hibernate Validator 3.x (legacy).
On a side note, if you are using SVN or any other traditional SCM, I highly recommend you to learn Git. That's probably the best investment you can make even above another framework :)
> 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: legacy
> Affects Versions: 3.0.0.ga
> Environment: Any
> Reporter: Mike Quilleash
> Fix For: 3.2.0
>
>
> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list