|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hardy, can you provide some more information, on what's the problem with Validator#validateValue? Otherwise, it's hard to follow the discussion. And second, why would this (per se) lead to constrain implementation behaving differently?
Sorry for stressing this, but I'm quite a bit disappointed that you simply reject this issue even if some community member(s) would like/need this method. Maybe there's not just "a single/best way" to implement validators.... why not leave this to the community on how to implement validators? If it's possible to do via unwrap() why not simply provide a shortcut method for this? It definitely wouldn't hurt.
And as explained in https://forum.hibernate.org/viewtopic.php?f=26&t=1012111 there are use cases for this. In my situation it's not really acceptable to require any cross-field validations to appear on class level. This would bloat the class declaration with annotations, double the amount of code to write for the end user and hence would make the source code much harder to read and understand...