November 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10456) CLONE - rich:messages displays messages multiple times

by Ilya Shaikovsky (JIRA)

CLONE - rich:messages displays messages multiple times ------------------------------------------------------ Key: RF-10456 URL: https://issues.jboss.org/browse/RF-10456 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 3.3.0, 3.3.1, 3.3.2.CR1, 3.3.2.GA, 3.3.2.SR1, 3.3.3.BETA1, 3.3.3.CR1, 3.3.3.Final Environment: Richfaces 3.3.0 upwards with integrated Spring Webflow (version 2.0.5) and Hibernate Validator 4.0.2. Reporter: Ilya Shaikovsky Assignee: Alexander Smirnov Fix For: 3.Future Using a graphValidator, I set up a bean with Hibernate Validator annotations. When multiple fields fail validation; the <rich:messages /> tag outputs the error messages multiple times. It seems as though the message is displayed based on the number of failed fields. For example; when 2 fields fail, it will display both error messages twice. If 3 fields fail, it'll display all 3 messages 3 times, and so on. I have managed to replicate the same error in versions 3.3.0 to 3.3.3. I have not tried >4 as we need a stable release. This may mean it could already be fixed in version 4; but I am submitting this issue regardless. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
30
0 / 0

[JBoss JIRA] Created: (RF-7344) Add controls for where in the header loaded scripts are placed

by Jay Balunas (JIRA)

Add controls for where in the header loaded scripts are placed -------------------------------------------------------------- Key: RF-7344 URL: https://jira.jboss.org/jira/browse/RF-7344 Project: RichFaces Issue Type: Task Components: browser compatibility, core Affects Versions: 3.3.1 Environment: IE8 Reporter: Jay Balunas Fix For: 3.3.2.CR1 IE8 requires some header content be located at the very top of the header. Because RichFaces places some of the loaded scripts first this can break. For example "<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />" will be ignored if not the first element after the header. Although the work around can be to just place the value in the header directly "<header name="X-UA-Compatible">IE=EmulateIE7</header>", RichFaces should have a way to control the location of the scripts in the header. This could take the form of a new context param or perhaps a tag that RF can trigger off of for default script placement. If not there behavior is defaulted to current. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

7
8
0 / 0

[JBoss JIRA] Created: (RF-11306) [rich:tabPanel] allow usage of form-elements inside tabs

by Rene O (JIRA)

[rich:tabPanel] allow usage of form-elements inside tabs -------------------------------------------------------- Key: RF-11306 URL: https://issues.jboss.org/browse/RF-11306 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Rene O Currently you must surround <rich:tabPanel> with <h:form>-element if you use switchType="ajax" or switchType="server". It should be possible, like in Richfaces 3, that a form-element outside of rich:tabPanel is not needed. A common usecase is the usage of an include-fragment which contains a form. <rich:tabPanel switchType="ajax"> <rich:tab> <h:form if="form1"> ... </h:form> </rich:tab> <rich:tab> <ui:include .../> </rich:tab> </rich:tabPanel> definition of include: <ui:composition > ... <h:form if="formOfInclude"> ... </h:form> </ui:composition > Currently it is not possible to design the pages in such way cause of nesting form-elements -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (RF-10197) Right click menu - rich:contextMenu - should be supported for 4.0.0

by Devinder Singh (JIRA)

Right click menu - rich:contextMenu - should be supported for 4.0.0 ------------------------------------------------------------------- Key: RF-10197 URL: https://issues.jboss.org/browse/RF-10197 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.0.0.Milestone5 Environment: Windows Reporter: Devinder Singh rich:contextMenu is available in 3.x release but not yet supported in 4.0. As it enables right click menus on JSF components, it's a very useful feature that can be used in wide variety of applications -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

18
24
0 / 0

[JBoss JIRA] (RF-11657) Better integration with JBossAS 7.1

by Juergen Zimmermann (Created) (JIRA)

Better integration with JBossAS 7.1 ----------------------------------- Key: RF-11657 URL: https://issues.jboss.org/browse/RF-11657 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution, compatibility Affects Versions: 4.1.0.Milestone3 Reporter: Juergen Zimmermann JBossAS 7.1 contains Google Guava 10.0.x (in addition to sac-1.3.jar and cssparser-0.9.5.jar). Guava can be reused in RichFaces instead of doubling it in WEB-INF/lib. The solution is pretty simple: In richfaces-core-impl-VERSION.jar the file META-INF/MANIFEST.MF already contains the line "Dependencies: ...". This line has to be extended by just ",com.google.guava" as follows: Dependencies: org.w3c.css.sac,net.sourceforge.cssparser,com.google.guava That's all and from now on RichFaces doesn't require the distribution of Google Guava in WEB-INF/lib when the platform is JBossAS 7.1. Please see also https://issues.jboss.org/browse/AS7-1809. Be aware that there is no blank after the comma between net.sourceforge.cssparser and com.google.guava. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
7
0 / 0

[JBoss JIRA] (RF-11650) Upgrade to jQuery 1.7

by Lukáš Fryč (Created) (JIRA)

Upgrade to jQuery 1.7 --------------------- Key: RF-11650 URL: https://issues.jboss.org/browse/RF-11650 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.CR1 Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] (RF-11529) a4j:support in rich:datatable JS crash in Chrome with limitToList="true"

by Stef Klaassen (Created) (JIRA)

a4j:support in rich:datatable JS crash in Chrome with limitToList="true" ------------------------------------------------------------------------ Key: RF-11529 URL: https://issues.jboss.org/browse/RF-11529 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Tomcat 7, RichFaces 3.3.3.Final Reporter: Stef Klaassen Priority: Minor I've got a Datatable in which I have a column that contains a tomahawk selectOneRadio. In this selectOneRadio is a a4j:support that has an onclick event to update some components. On this support-tag I had the limitToList-attribute set to true. This works fine in FF and IE, but today I tested it in Chrome and I saw that the Javascript wasn't executed anymore. When I click a radiobutton first, which makes another button in the next column dissapear, all goes well. But when I click another radiobutton that should make the next column button reappear again, it fails. I get the following error in chrome: Uncaught Error: Uncaught Error: NOT_SUPPORTED_ERR: DOM Exception 9 3_3_3.Finalorg.ajax4jsf.javascript.AjaxScript.html:121 which points at this line: var importednode=window.document.importNode(newnode,true);LOG.debug("Replace content of node by replaceChild()");var oldGetElementById=null;A4J.AJAX.TestReplacedGetElementByIdVisibility();if(!A4J.AJAX._testReplacedGetElementByIdVisibility){LOG.debug("Temporarily substituting document.getElementById() to work around WebKit issue");oldGetElementById=document.getElementById;document.getElementById=function(id){var elt=oldGetElementById.apply(document,arguments);if(!elt){var id=arguments[0];LOG.debug("Element [@id='"+id+"'] was not found in document, trying to locate XPath match");try{var result=importednode.ownerDocument.evaluate("//*[@id='"+id+"']",importednode,null,XPathResult.ANY_UNORDERED_NODE_TYPE);if(result){elt=result.singleNodeValue;} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
7
0 / 0

[JBoss JIRA] (RF-11675) Showcase and rich:dataTable - delayed sorting

by Jan Papousek (Created) (JIRA)

Showcase and rich:dataTable - delayed sorting --------------------------------------------- Key: RF-11675 URL: https://issues.jboss.org/browse/RF-11675 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables, showcase Affects Versions: 4.1.0.Milestone4 Environment: Firefox 7.0.1 JBoss AS 7.0.2 Reporter: Jan Papousek After the first clicking on the sorting link in the table header, nothing happens. User has to click twice to make the column sorted. It can be reproduced in Showcase - http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dataTa.... This bug doesn't occur in the last downloadable snapshat (richfaces-showcase-4.1.0-20111111.110230-135-jbas7.war), but it can be found when you build showcase from GitHub repo manually. It works correctly in Metamer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
10
0 / 0

[JBoss JIRA] (RF-11688) Showase on Openshift Express -> java.lang.OutOfMemoryError: PermGen space

by Jan Papousek (Created) (JIRA)

Showase on Openshift Express -> java.lang.OutOfMemoryError: PermGen space ------------------------------------------------------------------------- Key: RF-11688 URL: https://issues.jboss.org/browse/RF-11688 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.CR1 Reporter: Jan Papousek Trying to deploy showcase CR1 on openshift express (via git repository), the server throws OutOfMemoryError. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] (RF-11713) Showcase and rich:accordion - the "view source" link is hidden

by Jan Papousek (Created) (JIRA)

Showcase and rich:accordion - the "view source" link is hidden -------------------------------------------------------------- Key: RF-11713 URL: https://issues.jboss.org/browse/RF-11713 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.CR1 Environment: Firefox 7.0 Google Chrome Reporter: Jan Papousek Priority: Optional The "view source" link is hidden behind the rich:accordion component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2011