[
http://opensource.atlassian.com/projects/hibernate/browse/HV-228?page=com...
]
Ken Egervari commented on HV-228:
---------------------------------
You guys don't have to stick to what's defined there... you can actually expand on
it, just like your sister projects have. Hibernate provides more than JPA specifies. I
don't see a problem here :)
If you ask me, standards are lame and bloated. What really matters is that people get a
tool that works for them in practice. I think it's dumb to wait a for a standard that
eventually adds these things in 4 years too late. EJB 3.0 anyone?
I dunno how the architecture works on your end... but from my end, this is just an
exception thrown by your validator project. It really isn't possible to just add more
into the toString() method? You already have an array of invalidValues[] - we can just
iterate through that and print them. It's really very simple, and man... just think of
the people that would LOVE you for doing this.
I think in the grand scheme of things, will make your framework 10x easier to test with,
and will save people probably hours of time over the course of a long project, not to
mention reducing frustration levels. This is a very, very good idea. Please find a way to
implement it. Please :))))))
InvalidateStateException needs to show the error messages in the
message when it's thrown
-----------------------------------------------------------------------------------------
Key: HV-228
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-228
Project: Hibernate Validator
Issue Type: New Feature
Affects Versions: 3.1.0.GA
Reporter: Ken Egervari
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I dunno if you fixed this in 4.0 releases. To make testing easier, I think the error
messages should be viewable when the exception is thrown. I know it's possible to
inspect the exception for these errors, but within a unit test, this is just too much work
and it's annoying.
In practice, we create all these objects and do tests. Sometimes these objects get sent
to the database and are saved.
Now, let's say 3 validation constraints aren't met. On the outset, the developer
is 100% blind and must code in a try/catch and print out the list of errors. When this
happens over and over and over... it's just tedious. When a test fails because an
unexpected validation exception is thrown, I don't want to have to do this - I want to
instantly see what went wrong so I can make the changes to my test case and run it
quickly.
I think this change would facilitate much faster test/code cycles, and it shouldn't
be hard to add in.
Thanks
--
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