[
http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com....
]
Geoffrey De Smet commented on HV-24:
------------------------------------
1) While developing my testcases I frequently run into a stacktrace of
InvalidStateException and it's time consuming to figure out what I forgot on my dummy
testdata I inserted in my new testcase.
2) In theory our validation errors can't occur on production, because our swing client
prohibts sending invalid data (based on the hibernate validator).
In practice our swing client can't deal with @AssertTrue automatically (because
it's not property bound) and we sometimes forget to code those constraints. So the
stacktraces do show up in the log.
Even a simple clue in the stacktrace message, like "MyBeanClass [myProp1 @NotNull,
myProp2 @Size(5)]" would be great :)
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