[
https://issues.jboss.org/browse/RF-12943?page=com.atlassian.jira.plugin.s...
]
Brian Leathem resolved RF-12943.
--------------------------------
Fix Version/s: (was: 5-Tracking)
Resolution: Done
The tableState was being saved and re-applied on every request, which was overriding the
manually set backing bean filter (and sorting) values.
To resolve this issue, I prevented the table state from being saved when not bound to a
backing bean.
ExtendedDataTable: clearing of filter input doesnt work correctly
-----------------------------------------------------------------
Key: RF-12943
URL:
https://issues.jboss.org/browse/RF-12943
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
Attachments: JSF2-RichFaces-Test.zip
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" has a problem such 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.
--
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