April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12732) tabindex on rich:tabPanel

by Ricardo Martinelli Oliveira (JIRA)

[ https://issues.jboss.org/browse/RF-12732?page=com.atlassian.jira.plugin.s... ] Ricardo Martinelli Oliveira updated RF-12732: --------------------------------------------- Affects Version/s: 4.2.3.Final Description: Customer Dekra SE (acct# 1154941, no TAM, no SRM, not Strategic) requested an improvement in the <rich:tabPanel> described below: "From the last element inside richfaces tabpanel we would like to tab to the next tab flap. From there either: - press tab again or use the arrow keys to navigate the flaps - press enter to navigate to the contend of the tab that whoose flap tab focus Moreover that last element might be a rich:autocomplete instead of h:input" was: >From the last element inside richfaces tabpanel we would like to tab to the next tab flap. From there either: - press tab again or use the arrow keys to navigate the flaps - press enter to navigate to the contend of the tab that whoose flap tab focus Moreover that last element might be a rich:autocomplete instead of h:input Component/s: component-output component-panels-layout-themes > tabindex on rich:tabPanel > ------------------------- > > Key: RF-12732 > URL: https://issues.jboss.org/browse/RF-12732 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output, component-panels-layout-themes > Affects Versions: 4.2.3.Final > Reporter: Alexander Kunkel > Fix For: 5-Tracking > > > Customer Dekra SE (acct# 1154941, no TAM, no SRM, not Strategic) requested an improvement in the <rich:tabPanel> described below: > "From the last element inside richfaces tabpanel we would like to tab to the next tab flap. From there either: > - press tab again or use the arrow keys to navigate the flaps > - press enter to navigate to the contend of the tab that whoose flap tab focus Moreover that last element might be a rich:autocomplete instead of h:input" -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12921) rich:validator: created message is escaped, even if the message component should not be escaped

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-12921?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-12921: ---------------------------------- No, it isn't a regression. Check the note in steps to reproduce. > rich:validator: created message is escaped, even if the message component should not be escaped > ----------------------------------------------------------------------------------------------- > > Key: RF-12921 > URL: https://issues.jboss.org/browse/RF-12921 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Priority: Minor > Fix For: 4.3.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The created message is always escaped, even if the message component has its attribute @escape=false. > Message components: rich:message, rich:messages, rich:notifyMessage, rich:notifyMessages. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12928) ExtendedDataTable: columnsOrder doesnt work after changing order

by dako test (JIRA)

[ https://issues.jboss.org/browse/RF-12928?page=com.atlassian.jira.plugin.s... ] dako test updated RF-12928: --------------------------- Description: According to the resolved bug RF-11776 I tried the attribute columnsOrder in ExtendedDataTable. I have a simple test case with a data table and an action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. I have appended a test project to reproduce. In this test project I have an a4j ajax button and an simple button, both arent working. Best regards was: According to the resolved bug RF-11776 I tried the attribute columnsOrder in ExtendedDataTable. I have a simple test case with a data table and a action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. I have appended a test project to reproduce. Best regards > ExtendedDataTable: columnsOrder doesnt work after changing order > ---------------------------------------------------------------- > > Key: RF-12928 > URL: https://issues.jboss.org/browse/RF-12928 > 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 test > Attachments: JSF2-RichFaces-Test.zip > > > According to the resolved bug RF-11776 I tried the attribute columnsOrder in ExtendedDataTable. > I have a simple test case with a data table and an action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. > I have appended a test project to reproduce. In this test project I have an a4j ajax button and an simple button, both arent working. > Best regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12928) ExtendedDataTable: columnsOrder doesnt work after changing order

by dako test (JIRA)

dako test created RF-12928: ------------------------------ Summary: ExtendedDataTable: columnsOrder doesnt work after changing order Key: RF-12928 URL: https://issues.jboss.org/browse/RF-12928 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 test Attachments: JSF2-RichFaces-Test.zip According to the resolved bug RF-11776 I tried the attribute columnsOrder in ExtendedDataTable. I have a simple test case with a data table and a action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. I have appended a test project to reproduce. Best regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12928) ExtendedDataTable: columnsOrder doesnt work after changing order

by dako test (JIRA)

[ https://issues.jboss.org/browse/RF-12928?page=com.atlassian.jira.plugin.s... ] dako test updated RF-12928: --------------------------- Attachment: JSF2-RichFaces-Test.zip Test project to reproduce the bug. > ExtendedDataTable: columnsOrder doesnt work after changing order > ---------------------------------------------------------------- > > Key: RF-12928 > URL: https://issues.jboss.org/browse/RF-12928 > 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 test > Attachments: JSF2-RichFaces-Test.zip > > > According to the resolved bug RF-11776 I tried the attribute columnsOrder in ExtendedDataTable. > I have a simple test case with a data table and a action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. > I have appended a test project to reproduce. > Best regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12783) Upgrade compiler plugin to 3.1

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12783: ---------------------------- Fix Version/s: 5-Tracking (was: 5.0.0.Alpha1) > Upgrade compiler plugin to 3.1 > ------------------------------ > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12783) Upgrade compiler plugin to 3.1

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12783: --------------------------------- The {{maven-compiler-plugin:3.1}} still contains this bug: http://jira.codehaus.org/browse/MCOMPILER-187?focusedCommentId=323828&pag... > Upgrade compiler plugin to 3.1 > ------------------------------ > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12757) build/pom.xml contains non-unique dependencies

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12757?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12757 at 4/17/13 8:06 AM: ---------------------------------------------------------- This issue was resolved by moving imports to richfaces-parent ({{/pom.xml}}), while the dependency management for this artifacts is left in *build BOM* ({{/build/pom.xml}}) was (Author: lfryc): This issue was resolved by moving imports to {{/pom.xml}}, while the dependency management for this artifacts is left in *build BOM* ({{/build/pom.xml}}) > build/pom.xml contains non-unique dependencies > ---------------------------------------------- > > Key: RF-12757 > URL: https://issues.jboss.org/browse/RF-12757 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > build/pom.xml [1] contains jboss-javaee-6.0 and jboss-javaee-web-6.0 twice in the dependencyManagement section which is not allowed in Maven. Once it has default scope and once import. > [1] https://github.com/richfaces/richfaces5/blob/master/build/pom.xml -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12757) build/pom.xml contains non-unique dependencies

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12757?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12757 at 4/17/13 8:06 AM: ---------------------------------------------------------- This issue was resolved by moving imports to *richfaces-parent* ({{/pom.xml}}), while the dependency management for this artifacts is left in *build BOM* ({{/build/pom.xml}}) was (Author: lfryc): This issue was resolved by moving imports to richfaces-parent ({{/pom.xml}}), while the dependency management for this artifacts is left in *build BOM* ({{/build/pom.xml}}) > build/pom.xml contains non-unique dependencies > ---------------------------------------------- > > Key: RF-12757 > URL: https://issues.jboss.org/browse/RF-12757 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > build/pom.xml [1] contains jboss-javaee-6.0 and jboss-javaee-web-6.0 twice in the dependencyManagement section which is not allowed in Maven. Once it has default scope and once import. > [1] https://github.com/richfaces/richfaces5/blob/master/build/pom.xml -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12757) build/pom.xml contains non-unique dependencies

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12757?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12757: --------------------------------- This issue was resolved by moving imports to {{/pom.xml}}, while the dependency management for this artifacts is left in *build BOM* ({{/build/pom.xml}}) > build/pom.xml contains non-unique dependencies > ---------------------------------------------- > > Key: RF-12757 > URL: https://issues.jboss.org/browse/RF-12757 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > build/pom.xml [1] contains jboss-javaee-6.0 and jboss-javaee-web-6.0 twice in the dependencyManagement section which is not allowed in Maven. Once it has default scope and once import. > [1] https://github.com/richfaces/richfaces5/blob/master/build/pom.xml -- 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, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2013