[
https://issues.apache.org/jira/browse/TAPESTRY-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-353:
-----------------------------------
Fix Version/s: (was: 4.1.2)
4.2
> Validator API for easy re-validation of data
> --------------------------------------------
>
> Key: TAPESTRY-353
> URL: https://issues.apache.org/jira/browse/TAPESTRY-353
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Fix For: 4.2
>
>
> It would be nice if there was a reasonable way to reuse a Validator to do
> business-logic level validation. Perhaps add a method to the Validator
> interface:
> public boolean isValid(Object object);
> For background: I'm building a multi-page wizard that edits a common shared
> data (stored as an ASO). At the end of the wizard, I need to check that all
> data from all pages is valid (the user is allowed to jump around in the
> wizard). I'm finding that I'm re-implementing a lot of validation checks in
> code, duplicating logic already associated with the fields (in the form of
> validator strings like "required,minLength=5").
> What would be nice would be to have an easy way to re-run the validations,
> just to generate a boolean. At the core of this is combining the current
> value for the component (possibly extracted right out of the business object)
> with the list of validators.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
