myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (EXTVAL-47) Class based validation as in JSR 303
Date Thu, 11 Jun 2009 09:41:07 GMT

    [ https://issues.apache.org/jira/browse/EXTVAL-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718377#action_12718377
] 

Gerhard Petracek commented on EXTVAL-47:
----------------------------------------

it will be possible with the jsr 303 integration module of extval x.x.3 (the next release)
which will be available for jsf 1.1.x. 1.2.x and 2.0.x

so there will be the following validation modules:
 - property-validation
 - bean-validation

however, if you have a nice idea for special extval constraints which perform class based
validation, please setup a proposal e.g. at:
http://wiki.apache.org/myfaces/Extensions/Validator/DevDoc/Drafts


> Class based validation as in JSR 303
> ------------------------------------
>
>                 Key: EXTVAL-47
>                 URL: https://issues.apache.org/jira/browse/EXTVAL-47
>             Project: MyFaces Extensions Validator
>          Issue Type: Wish
>            Reporter: Stefan Meyer
>
> How is it possible to do class based validation as in jsr 303. As far as I understand
jsr 303 is validating a populated bean while jsf is validating before population - hence all
those issues.
> How about adding another phase for validation after model update? keeping the model valid
at all times is a nice feature. But when you create a bean - a customer or what ever - it
will be empty at first and surely not valid.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message