-
Hi,
the current release 1.40 only interprets annotations on field level. I just committed the required changes to SVN to support property level annotations too.
Regards,
Seb.
2009-11-04 16:02:56 UTC in OVal
-
sebthom committed revision 471 to the OVal SVN repository, changing 3 files.
2009-11-04 16:01:43 UTC in OVal
-
sebthom committed revision 470 to the OVal SVN repository, changing 4 files.
2009-11-02 19:18:39 UTC in OVal
-
Hi Eric,
I just committed a change to SVN that avoids logging of the NoSuchMethodException. The exception is irrelevant in this context. the problem is that the reflection API does not allow you to check if a method exists without generating this exception.
Setting the log levels depends on which logging framework you are using. by default oval uses JDK logging.
Regards,
Seb.
2009-11-02 19:06:09 UTC in OVal
-
sebthom committed revision 469 to the OVal SVN repository, changing 2 files.
2009-11-02 19:03:58 UTC in OVal
-
sebthom committed revision 468 to the OVal SVN repository, changing 1 files.
2009-11-02 18:34:31 UTC in OVal
-
Hi Eric,
you must check the ValidationFailedException's cause to see what the reason is. This exception does not mean that a validated object is invalid, but the Validator could not perform the validation at all. E.g. because of security issues when retrieving values via reflection etc.
Regards,
Seb.
2009-10-26 14:55:32 UTC in OVal
-
sebthom committed revision 467 to the OVal SVN repository, changing 19 files.
2009-10-23 19:11:07 UTC in OVal
-
Hi Eric,
please ignore my last post. You are right, the violation message was missing. I mixed this one up with AssertFieldConstraints.
You can access the underlying violations of an AssertValid violation by accessing constraintViolation.getCauses()
Regards,
Seb.
2009-10-23 19:11:03 UTC in OVal
-
Hi Michenux,
that is currently not possible. You could try to extend Validator class and modify it for this behaviour. If you provide us a concrete example I can see if I can help.
Regards,
Seb.
2009-10-23 15:47:44 UTC in OVal
