[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] Mike Quilleash commented on HV-24: ---------------------------------- In my scenario InvalidStateException is generally a programming error (someone forgot to set something). It is a web application so a lot of validation is handled by Seam and it marks the appropriate control as invalid which is all fine. But properties and related objects are created or set in the business code (default values etc) and sometimes a developer will forget to set one of these properties. When the validation fires an exception is caught and is redirected to an exception page with stack trace, component tree, context state etc. If the InvalidValues (properties and actual values) were in the message of the exception then it would become much faster to determine the problem, rather than having to find the right place to debug in the code. Additionally, and this is probably more important, outside of development if it happens in production you often only have the stack trace to work with if something really nasty happens so as much information as possible is important. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] Nicolás Lichtmaier commented on HV-24: -------------------------------------- A developer readable flat version of what has gone wrong is clearly useful. In many cases one would want to use "validator" annotated classes without a GUI, and it would be great to be able to rely just on a logged "printStackTrace" (as is standard in exception classes) to see what has gone wrong. It's nice to have this for development early stages too. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] Nicolás Lichtmaier commented on HV-24: -------------------------------------- Of course, and I might decide just logging the printStackTrace output of exceptions in general (no just that one). For any other exception, the "printStackTrace" method will try to represent all the problem. We are not talking about a nice user-visible display, just a small list of the failed tests. Of course is not must-to-have feature, but in my experiencie it would be a nice thing to have. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] Hardy Ferentschik updated HV-24: -------------------------------- Component/s: (was: engine) legacy Moved issue into legacy component. This issue applies to codebase prior 4.x -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] Geoffrey De Smet commented on HV-24: ------------------------------------ +1 for Tomasz change. This issue hurts a little bit every so often (it's a "a hundred papercuts" issue) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] Emmanuel Bernard commented on HV-24: ------------------------------------ Release 3.2 has not been released and will likely not be as we have moved to the 4.x codebase a year and a half ago. But if you provide a pull-request based on http://github.com/hibernate/hibernate-validator (specifically hibernate-validator-legacy). We can apply it and it will be part of the next 4.x release. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-24?page=com.... ] 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 :) -- 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