[
http://opensource.atlassian.com/projects/hibernate/browse/HV-476?page=com...
]
Gunnar Morling commented on HV-476:
-----------------------------------
Ah, that's an interesting case. The problem was caused by a synthetic (or bridge)
method added to the byte code of class {{B}} by the compiler in order to implement the
covariant return type of {{getValue()}}. In 4.2 this is indeed fixed already, as synthetic
methods are now generally excluded from any processing in
{{BeanMetaDataImpl#initMethodConstraints()}}.
Min Max and other annotations are causing exceptions in Parametrized
class hierarchies
--------------------------------------------------------------------------------------
Key: HV-476
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-476
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.1.0.Final
Reporter: Vitaly Polonetsky
Attachments: Test.java
I'm getting
javax.validation.UnexpectedTypeException: No validator could be found for type:
java.lang.Object
exception for the supplied test case.
And the more interesting part is that it depends on the order of the execution of the
validations.
--
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