You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Christophe FOIRET (JIRA)" <ji...@apache.org> on 2009/04/28 11:47:30 UTC
[jira] Created: (CLK-541) Required Field in a Form which has been
disabled
Required Field in a Form which has been disabled
------------------------------------------------
Key: CLK-541
URL: https://issues.apache.org/jira/browse/CLK-541
Project: Click
Issue Type: Bug
Components: core
Affects Versions: 1.5.1
Environment: Linx Apache mySQL
Reporter: Christophe FOIRET
When i create a field in a form which is disabled and becomes enabled and required after change on another field, the required field is not considered in the validation form as a required field.
The field has an asterisk but there is no error message if this one is not filled and i can update my JavaBean without control. Could you correct this bug in the 1.5.1 version ?
Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CLK-541) Required Field in a Form which has been
disabled
Posted by "Bob Schellink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLK-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Schellink closed CLK-541.
-----------------------------
Resolution: Won't Fix
not a bug
> Required Field in a Form which has been disabled
> ------------------------------------------------
>
> Key: CLK-541
> URL: https://issues.apache.org/jira/browse/CLK-541
> Project: Click
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.1
> Environment: Linx Apache mySQL
> Reporter: Christophe FOIRET
>
> When i create a field in a form which is disabled and becomes enabled and required after change on another field, the required field is not considered in the validation form as a required field.
> The field has an asterisk but there is no error message if this one is not filled and i can update my JavaBean without control. Could you correct this bug in the 1.5.1 version ?
> Thanks
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.