You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Bob Schellink (JIRA)" <ji...@apache.org> on 2009/07/26 19:19:14 UTC
[jira] Resolved: (CLK-572) Improve Form validation for subclasses
to implement business and cross-field validation
[ https://issues.apache.org/jira/browse/CLK-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Schellink resolved CLK-572.
-------------------------------
Resolution: Fixed
fixed in trunk
> Improve Form validation for subclasses to implement business and cross-field validation
> ---------------------------------------------------------------------------------------
>
> Key: CLK-572
> URL: https://issues.apache.org/jira/browse/CLK-572
> Project: Click
> Issue Type: Improvement
> Components: core
> Affects Versions: 2.1.0 RC1
> Reporter: Bob Schellink
> Assignee: Bob Schellink
> Fix For: 2.1.0
>
>
> Its currently not possible for Form subclasses to override and implement custom business and cross-field validation logic in the #validate method, because the validate method is invoked *before* the Field values are processed and bound to request values.
> Proposed solution is to rename the current Form.validate() method to Form.validateFileUpload (because that is what is currently does) and introduce a new empty validate method which subclasses can override. This is consistent with the approach taken by Field which also provide an empty validate method which subclasses can implement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.