[JIRA] Resolved: (CLK-497) FieldSet isDisabled and isReadonly methods broken

["Bob Schellink (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/click/browse/CLK-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Schellink resolved CLK-497.
-------------------------------

    Resolution: Fixed

The test cases and fix have been checked in. The FieldSet is now correctly set as the parent.

Closing the issue for now as we can always revisit the cascade/block issue at a later stage.

> FieldSet isDisabled and isReadonly methods broken
> -------------------------------------------------
>
>                 Key: CLK-497
>                 URL: http://issues.apache.org/click/browse/CLK-497
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.1, 1.5.1
>         Environment: Windows XP, Java 6
>            Reporter: James P Brown
>            Assignee: Bob Schellink
>             Fix For: 2.1.0, 2.0.2, 1.5.2
>
>         Attachments: FieldSet_isDisabled_isReadonly_bug.zip
>
>
> The FieldSet is supposed to force its child components to be disabled/readonly when it is set to disabled/readonly. I did not observe this when I attempted to create a FieldSet with a child component.
> I believe the code to support this is not working as anticipated. The Field class has modified methods for isDisabled/isReadonly that specifically check if the parent component (i.e. container) is an instanceof FieldSet (or Form, which is working AFAIK). The problem is that the design of FieldSet relies on an instance of its private inner class FieldSet.InnerContainerField for managing those child elements. When I step through the code in debug mode, the class instance is of this inner class type (InnerContainerField) not FieldSet. Since InnerContainerField is not a type of FieldSet, the subsequent logic is ignored.

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