[JBoss JIRA] (RF-12943) ExtendedDataTable: clearing of filter input doesnt work correctly
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12943?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12943:
-------------------------------
Summary: ExtendedDataTable: clearing of filter input doesnt work correctly (was: ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly)
> 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, 5-Tracking
>
> 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" 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.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13133) ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13133:
------------------------------------
Cloned from RF-12943 so that we have one bug per issue.
> 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
12 years, 7 months
[JBoss JIRA] (RF-13133) ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13133:
-------------------------------
Original Estimate: 1 hour (was: 2 hours)
Remaining Estimate: 1 hour (was: 2 hours)
> 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: 1 hour
> Remaining Estimate: 1 hour
>
> 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
12 years, 7 months
[JBoss JIRA] (RF-13133) ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.s... ]
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
12 years, 7 months
[JBoss JIRA] (RF-13133) ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13133:
-------------------------------
Summary: ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns (was: ExtendedDataTable: filterType custom filter input doesn't work when mixing custom and built-in filter columns)
> 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.
> 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.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13133) ExtendedDataTable: filterType custom filter input doesn't work when mixing custom and built-in filter columns
by Brian Leathem (JIRA)
Brian Leathem created RF-13133:
----------------------------------
Summary: ExtendedDataTable: filterType custom filter input 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
Fix For: 4.3.4, 5-Tracking
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.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13113) org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13113?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13113:
----------------------------
Fix Version/s: cdk-4.5.0.Alpha2
(was: 4.3.4)
> org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0
> -----------------------------------------------------------------------------
>
> Key: RF-13113
> URL: https://issues.jboss.org/browse/RF-13113
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: cdk
> Reporter: Tomas Repel
> Assignee: Lukáš Fryč
> Fix For: cdk-4.5.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Description of problem:
> org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0:3.0.1.Final-redhat-1, which is available only in jboss-eap-6.0.1-maven repository.
> This causes failure when building Seam distribution from sources. In EAP 6.1 repository there is available org.jboss.spec : jboss-javaee-web-6.0 : 3.0.2.Final-redhat-3
--
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
12 years, 7 months