bval-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Benson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BVAL-107) Validation of Return-Values
Date Mon, 25 Jun 2012 19:01:45 GMT

    [ https://issues.apache.org/jira/browse/BVAL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400777#comment-13400777
] 

Matt Benson commented on BVAL-107:
----------------------------------

Hi, guys.  This was a documentation oversight on my part.  It was determined that, method
validation being an optional feature, it was reasonable that the user be required to explicitly
enable it, so in v0.4, you need to set the property {{apache.bval.metabean-factory-classnames}}
to {{org.apache.bval.jsr303.extensions.MethodValidatorMetaBeanFactory}}.  The way this was
done on-the-fly at runtime was a little ugly in the code IMO.  It may be possible to reenable
the functionality for future versions; in any event method validation will be available by
default when Apache BVal implements the forthcoming Bean Validation 1.1 specification.  I'll
leave this issue open until we determine whether and how we can reenable.
                
> 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
>            Assignee: Matt Benson
>         Attachments: ValidationTest.jar, bval.zip
>
>
> 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

        

Mime
View raw message