bval-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Benson (JIRA)" <>
Subject [jira] [Commented] (BVAL-107) Validation of Return-Values
Date Fri, 22 Jun 2012 22:02:42 GMT


Matt Benson commented on BVAL-107:

Hello!  Having reconstructed a Maven project from the contents of the attached jar, it appears
that ConstraintValidationTest#testReturnValueToLong() fails even if I change the bval-jsr303
dependency version to 0.3-incubating.  Therefore I cannot reproduce that there is a true regression
at work.  I will continue to review the situation regarding whether the example should work
independently of the question of there being a regression from v0.3-incubating to v0.4.

> Validation of Return-Values
> ---------------------------
>                 Key: BVAL-107
>                 URL:
>             Project: BVal
>          Issue Type: Bug
>          Components: jsr303
>    Affects Versions: 0.4
>         Environment: JDK 1.6, Windows, Eclipse 3.7
>            Reporter: Sascha Vujevic
>         Attachments: ValidationTest.jar
> In the Test i have attached i have a @Size-Constraint on a method for validation of the
returnvalue. In version 0.3 of bval-jsr303 it worked.
> In version 0.4 there is a change in the code:
> The method org.apache.bval.jsr303.extensions.patchFactoryContextForMethodValidation is
no longer activ. Therefore all Jsr303MetaBeanFactory were no longer changed to MethodValidatorMetaBeanFactory.
> This has the affect that the method hasValidationConstraintsDefined() is used from Jsr303MetaBeanFactory
which checks if there is a Constraint on the Method. If it is, a exception is thrown "Property
%myMethod% does not follow javabean conventions".
> Mayby i use the annotions for validating returnvalues in a wrong way.
> I have attached an example.
> Thank you for your help.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message