[
https://issues.apache.org/jira/browse/BVAL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399702#comment-13399702
]
Matt Benson commented on BVAL-107:
----------------------------------
Any chance of something that runs and fails in the correct place? How does
this differ from the tests in
http://svn.apache.org/viewvc/bval/trunk/bval-jsr303/src/test/java/org/apache/bval/jsr303/extensions/MethodValidatorImplTest.java?view=markup,
for example?
Thanks!
> Validation of Return-Values
> ---------------------------
>
> Key: BVAL-107
> URL: https://issues.apache.org/jira/browse/BVAL-107
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
