[richfaces-issues] [JBoss JIRA] (RF-13133) ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns

[Brian Leathem (JIRA)]

     [ https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13133:
-------------------------------

    Description: 
According to my appended test project:

I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too.

  was:
According to my appended test project:

I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too.

The second problem with the input filter is that I can't clear this filter input text components by a a4j:commandButton. The table is correct filtered but the filter input text fields are not cleared.


    
> ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
> ------------------------------------------------------------------------------------------------
>
>                 Key: RF-13133
>                 URL: https://issues.jboss.org/browse/RF-13133
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.1
>         Environment: Tomcat 7, Mojarra 2.1.21
>            Reporter: dako ak
>            Assignee: Brian Leathem
>              Labels: testcase_provided
>             Fix For: 4.3.4, 5-Tracking
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> According to my appended test project:
> I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira