February 2013 - richfaces-issues - Jboss List Archives

[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: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > 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 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12792) ContextMenu - onkeydown attribute does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12792?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12792: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > ContextMenu - onkeydown attribute does not work > ----------------------------------------------- > > Key: RF-12792 > URL: https://issues.jboss.org/browse/RF-12792 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.0.Final > Environment: RichFaces 4.3.1-SNAPSHOT > Metamer 4.3.1-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Chrome 24.0.1312.69 @ Linux x86_64 > Reporter: Juraj Húska > Fix For: 4.3.1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The {{onkeydown}} attribute does not work. > Just note that {{onkeyup}} work just fine. -- 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

13 years, 6 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: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > 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 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12768: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Metamer: rich:tabPanel: Tabs are not clickable and can't be removed > ------------------------------------------------------------------- > > Key: RF-12768 > URL: https://issues.jboss.org/browse/RF-12768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Labels: richfaces4 > Fix For: 4.3.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed. -- 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

13 years, 6 months

1
0
0 / 0

[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: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > 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 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12774) a4j:commandLink does not set the styleClass when disabled

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12774?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12774: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > a4j:commandLink does not set the styleClass when disabled > --------------------------------------------------------- > > Key: RF-12774 > URL: https://issues.jboss.org/browse/RF-12774 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.Final > Reporter: Timothy Whitehead > Labels: a4j:commandLink, regression, richfaces, styleClass > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > I upgraded to 4.3.0.Final and when I use a disabled a4j:commandLink it renders with class="class org.richfaces.component.UICommandLink" I believe it was working correctly in 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

13 years, 6 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: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > 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 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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

13 years, 6 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: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > 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 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12760) rich:tabPanel does not work after ajax request

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12760?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12760: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > rich:tabPanel does not work after ajax request > ---------------------------------------------- > > Key: RF-12760 > URL: https://issues.jboss.org/browse/RF-12760 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.0.M2, 4.3.0.M3, 4.3.0.CR1, 4.3.0.CR2 > Environment: RichFaces 4.3.0.CR2 > Metamer 4.3.0-SNAPSHOT > Mojarra 2.1.7-jbossorg-2 > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 24.0.1312.56 @ Linux x86_64 > ----------------------------------------------------------- > Windows 7 - Chrome 24.0.1312.56 / IE 9. > Mojarra 2.1.17 > Richfaces 4.3.0.CR2 > Reporter: Adelmo Erick santos > Labels: regression > Fix For: 4.3.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When I submit a ajax request in a h:commandButtom within a tab with f:ajax them the tabPanel don´t switch tabs anymore. The problem is already reported in RF-10112. Sorry i´m from Brazil and my english very bad. > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j" > > > <h:head> > </h:head> > <h:body> > <h:form> > <rich:tabPanel> > <rich:tab header="cash"> > <h:commandButton value="Enter"> > <f:ajax event="click" render="@form"/> > </h:commandButton> > </rich:tab> > <rich:tab header="creditCard"> > <h:outputText value="Test"/> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {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

13 years, 6 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: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > 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 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > 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

13 years, 6 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 February 2013