February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12750) extendedDataTable make facet header clickable using default sortHandle

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12750?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12750: ------------------------------- Fix Version/s: 4.3.1 (was: 5-Tracking) > extendedDataTable make facet header clickable using default sortHandle > ---------------------------------------------------------------------- > > Key: RF-12750 > URL: https://issues.jboss.org/browse/RF-12750 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.0.M3 > Reporter: Marc A. Harnos > Priority: Minor > Labels: datatable, extendedDataTable, extended_datatable, extendeddatatable > Fix For: 4.3.1 > > > It would be nice, if the default sort handler on an extendedDataTable would also make the facet header clickable (like the sorting arrows span). -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12754) rich:validator message cannot be customized when using bean validation (via javax.faces.validator.BeanValidator.MESSAGE property)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12754?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12754: ------------------------------- Fix Version/s: 4.3.1 (was: 5-Tracking) > rich:validator message cannot be customized when using bean validation (via javax.faces.validator.BeanValidator.MESSAGE property) > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12754 > URL: https://issues.jboss.org/browse/RF-12754 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.0.CR1 > Environment: Glassfish 3.1.2.2, jdk7u9 > Reporter: Nejc G > Assignee: Brian Leathem > Labels: testcase_provided > Fix For: 4.3.1 > > Attachments: sample.rar > > > rich:validator clientside validation is ignoring javax.faces.validator.BeanValidator.MESSAGE property for messages. Standard validation without rich:validator works fine. Problem is there is no way to customize error (show label) hence making bean validation using this path nearly useless. > I have the aforementioned property in a property file, configured to be used through locale-config line in faces-config.xml. The line reads: > javax.faces.validator.BeanValidator.MESSAGE={1}: {0} > and as mentioned rich:validator only outputs {0} (that is msg from bean validation). Seems to me it doesn't behave as configured. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12758) ExtendedDatatable: horizontal scroll bar not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12758?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12758: ---------------------------------- Assignee: Pavol Pitonak [~ppitonak] Can you check if this is an issue with mojarra as well? > ExtendedDatatable: horizontal scroll bar not work > ------------------------------------------------- > > Key: RF-12758 > URL: https://issues.jboss.org/browse/RF-12758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.0.CR1 > Environment: Myfaces 2.1.10 , WebLogic 10.3.4 > Reporter: blam lam > Assignee: Pavol Pitonak > Labels: regression > > When the same xhtml page contains 2 extendedDatatables, the horizontal scroll bar stop function. > The problem does not appear in 4.2.1. It should a bug after 4.2.3 final. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12758) ExtendedDatatable: horizontal scroll bar not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12758?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12758: ------------------------------- Fix Version/s: (was: 5-Tracking) > ExtendedDatatable: horizontal scroll bar not work > ------------------------------------------------- > > Key: RF-12758 > URL: https://issues.jboss.org/browse/RF-12758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.0.CR1 > Environment: Myfaces 2.1.10 , WebLogic 10.3.4 > Reporter: blam lam > Labels: regression > > When the same xhtml page contains 2 extendedDatatables, the horizontal scroll bar stop function. > The problem does not appear in 4.2.1. It should a bug after 4.2.3 final. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12758) ExtendedDatatable: horizontal scroll bar not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12758?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12758: ------------------------------- Labels: regression (was: ) > ExtendedDatatable: horizontal scroll bar not work > ------------------------------------------------- > > Key: RF-12758 > URL: https://issues.jboss.org/browse/RF-12758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.0.CR1 > Environment: Myfaces 2.1.10 , WebLogic 10.3.4 > Reporter: blam lam > Labels: regression > Fix For: 5-Tracking > > > When the same xhtml page contains 2 extendedDatatables, the horizontal scroll bar stop function. > The problem does not appear in 4.2.1. It should a bug after 4.2.3 final. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12765: ------------------------------- Fix Version/s: 4.3.1 (was: 5-Tracking) > Rich:tabPanel not possible to switch tabs when only dynamic tabs are present > ---------------------------------------------------------------------------- > > Key: RF-12765 > URL: https://issues.jboss.org/browse/RF-12765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.M3, 4.3.0.CR2 > Environment: Linux, windows any browser Chrom, Mozilla > Reporter: Tali Han > Fix For: 4.3.1 > > > Rih:Tab panel functionality is broken. > If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. > Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. > richfaces/tabPanel/samples/dynamic-sample.xhtml > {code} > <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> > <ui:remove> > <rich:tab header="Static"> > This tab is static one. > > All of the following tabs are dynamically generated using a4j:repeat. > </rich:tab> > </ui:remove> > <a4j:repeat value="#{skinBean.skins}" var="skinName"> > > <rich:tab header="#{skinName}" name="#{skinName}"> > <f:facet name="header">#{skinName}</f:facet> > All the controls below are just standard JSF components skinned with RichFaces: > <hr /> > <h:form> > {code} -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12791) Update the quickstart pom files to match changes made in the jboss-jdf repository

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12791?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12791: ------------------------------- Fix Version/s: 4.3.1 > Update the quickstart pom files to match changes made in the jboss-jdf repository > --------------------------------------------------------------------------------- > > Key: RF-12791 > URL: https://issues.jboss.org/browse/RF-12791 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Fix For: 4.3.1 > > > There were numerous changes to the quickstart pom files: > - property names were shortened and standardized > - property versions were updated > - comments were standardized around product/community version numbers > It may be easiest just to copy and paste the corresponding jboss-jdf quickstart pom.xml files into your repository, however, these are the commits: > https://github.com/sgilda/quickstart/commit/ca2a7bea84262a7aa28b082760746... > https://github.com/sgilda/quickstart/commit/d951d07c1a2e980b0550ff62145cf... -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12789) TabPanel error after partial update with new tab

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12789: ------------------------------- Fix Version/s: 4.3.1 > TabPanel error after partial update with new tab > ------------------------------------------------ > > Key: RF-12789 > URL: https://issues.jboss.org/browse/RF-12789 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.0.CR2 > Environment: Mojarra 2.1.17, Tomcat 7.0.22, Java 1.7, Windows 7 > Reporter: Lutz Ulrich > Labels: Tab, TabPanel, dynamical-add > Fix For: 4.3.1 > > > Adding tabs dynamically (programatically) in partial requests results in errors. > The JavaScript code for all TabPanels and their child Tabs is added to HTML <body> using JavaScriptService.addScript(FacesContext, S), see DivPanelRenderer.writeJavaScript(), TabRenderer.doEncodeItemEnd() and TabRenderer.doEncodeEnd(). > The top-level <script> element in <body> won't be updated if a new Tab is added dynamically in a partial request. Thus, the script, new RichFaces.ui.Tab(...), for the new Tab is missing. > Similar problems arise if a TabPanel is added in a partial request. > All scripts, RichFaces.ui.Tab(...) and RichFaces.ui.TabPanel(...) should be rendered inline for partial update to work with new TabPanels and new Tabs. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12788) org.richfaces.javascript.QUnitTest fails in WFK 2.2

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12788?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12788: ------------------------------- Fix Version/s: 4.3.1 > org.richfaces.javascript.QUnitTest fails in WFK 2.2 > --------------------------------------------------- > > Key: RF-12788 > URL: https://issues.jboss.org/browse/RF-12788 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core, tests - unit > Affects Versions: 4.3.0.Final > Environment: WFK 2.2 > Reporter: Marek Novotny > Fix For: 4.3.1 > > Attachments: org.richfaces.javascript.QUnitTest.txt > > > we can see that CI job reports a few failed tests (8 from > 167) in org.richfaces.javascript.QUnitTest > {code} > Results : > Failed tests: testEvent(org.richfaces.javascript.QUnitTest): Failures:(..) > testPosition(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueRequest(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueGetSize(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueEmpty(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueClear(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueSubmitFirst(org.richfaces.javascript.QUnitTest): Failures:(..) > testBaseComponent(org.richfaces.javascript.QUnitTest): Failures:(..) > Tests run: 167, Failures: 8, Errors: 0, Skipped: 2 > Output from failed build is at > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/WFK/view/WFK-2.2/jo... > {code} -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12786) Showcase - rewrite readme to markdown

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12786?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12786: ---------------------------------- Assignee: Juraj Húska Than ks for volunteering to resolve this issue [~jhuska]! Not all OSS work is glorious ;) > Showcase - rewrite readme to markdown > ------------------------------------- > > Key: RF-12786 > URL: https://issues.jboss.org/browse/RF-12786 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.Final > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > Fix For: 4.3.1 > > > Please consider rewriting of showcase readme.txt to mark down syntax to be nicely parsed by GitHub. -- 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

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2013