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 2010/04/25 18:05:49 UTC
[jira] Created: (CLK-666) Adding controls to page or container
should replace existing control with the same name
Adding controls to page or container should replace existing control with the same name
---------------------------------------------------------------------------------------
Key: CLK-666
URL: https://issues.apache.org/jira/browse/CLK-666
Project: Click
Issue Type: Improvement
Components: core
Affects Versions: 2.1.0
Reporter: Bob Schellink
Assignee: Bob Schellink
Fix For: 2.2.0
When adding controls, Click throws an exception if the Page or Container already contains a control with the same name. Page and Panel models behave similarly.
This behavior protects users from accidentally adding controls with the same name, but at the same time doesn't work well for stateful pages where existing controls should be replaced.
The proposed change is to *not* throw an exception and simply replace the existing control or model object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CLK-666) Adding controls to page or container
should replace existing control with the same name
Posted by "Bob Schellink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLK-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Schellink resolved CLK-666.
-------------------------------
Resolution: Fixed
fixed in trunk
> Adding controls to page or container should replace existing control with the same name
> ---------------------------------------------------------------------------------------
>
> Key: CLK-666
> URL: https://issues.apache.org/jira/browse/CLK-666
> Project: Click
> Issue Type: Improvement
> Components: core
> Affects Versions: 2.1.0
> Reporter: Bob Schellink
> Assignee: Bob Schellink
> Fix For: 2.2.0
>
>
> When adding controls, Click throws an exception if the Page or Container already contains a control with the same name. Page and Panel models behave similarly.
> This behavior protects users from accidentally adding controls with the same name, but at the same time doesn't work well for stateful pages where existing controls should be replaced.
> The proposed change is to *not* throw an exception and simply replace the existing control or model object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.