November 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-11097) RichFaces showcase enhanced for the mobile web

by Jay Balunas (JIRA)

RichFaces showcase enhanced for the mobile web ---------------------------------------------- Key: RF-11097 URL: https://issues.jboss.org/browse/RF-11097 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: examples, mobile, showcase Reporter: Jay Balunas Assignee: Wesley Hales Priority: Critical Fix For: 4.1.0.Milestone2 The showcase should be enhanced to support the mobile web including device detection, orientations, transitions, and layout updates based on device type. Ideally this is the same application, but updated with this support. It would be a great example of how to add mobile web support to an existing web application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

10
12
0 / 0

[JBoss JIRA] Created: (RF-10227) autocomplete has no "nothingLabel"

by Juergen Zimmermann (JIRA)

autocomplete has no "nothingLabel" ---------------------------------- Key: RF-10227 URL: https://issues.jboss.org/browse/RF-10227 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Milestone5 Reporter: Juergen Zimmermann rich:autocomplete doesn't have a "nothingLabel" to indicate that there are no matches -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

6
9
0 / 0

[JBoss JIRA] (RF-11658) Upgrade hibernate validator to 4.2

by Marek Novotny (Created) (JIRA)

Upgrade hibernate validator to 4.2 ---------------------------------- Key: RF-11658 URL: https://issues.jboss.org/browse/RF-11658 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Reporter: Marek Novotny We need to use Hibernate Validator 4.2.0 and if I do upgrade with help of jboss-paren, Richfaces UI Components: validator ui project test fails. {noformat} Failed tests: testSubmitTooShortValue(org.richfaces.component.GraphValidationTest): testBeanLevelConstrain(org.richfaces.component.GraphValidationTest): testSubmitTooShortValue(org.richfaces.component.FacesBeanValidatorTest): testBeanLevelConstrain(org.richfaces.component.FacesBeanValidatorTest): Tests in error: testValidator[0](org.richfaces.javascript.client.validator.MaxValidatorTest): org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/String; testValidator[1](org.richfaces.javascript.client.validator.MaxValidatorTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testValidator[2](org.richfaces.javascript.client.validator.MaxValidatorTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testGetSingleValidator(org.richfaces.validator.BeanValidatorServiceConstrainsTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testGetNoValidator(org.richfaces.validator.BeanValidatorServiceConstrainsTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testValidatorMessageExtractor(org.richfaces.validator.BeanValidatorServiceConstrainsTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testGetConstrainsWithDefaulGroup(org.richfaces.validator.BeanValidatorServiceConstrainsTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testGetConstrainsWithNullGroup(org.richfaces.validator.BeanValidatorServiceConstrainsTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl testGetConstrainsWithCustomGroup(org.richfaces.validator.BeanValidatorServiceConstrainsTest): Could not initialize class org.hibernate.validator.engine.ConfigurationImpl {noformat} -- 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

12 years, 12 months

6
10
0 / 0

[JBoss JIRA] (RF-11710) rich:validator - selection size validation fails

by Jan Papousek (Created) (JIRA)

rich:validator - selection size validation fails ------------------------------------------------ Key: RF-11710 URL: https://issues.jboss.org/browse/RF-11710 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.1.0.CR1 Environment: RichFaces 4.1.0-SNAPSHOT Metamer 4.1.0-SNAPSHOT r.22936 Mojarra 2.1.3-SNAPSHOT JBoss AS 7.0.2.Final Java(TM) SE Runtime Environment 1.6.0_25-b06 @ Linux Firefox 7.0.1 @ Linux x86_64 RichFaces 4.1.0-SNAPSHOT Metamer 4.1.0-SNAPSHOT r.22936 Mojarra 2.1.3-SNAPSHOT Apache Tomcat 7.0.22 Java(TM) SE Runtime Environment 1.6.0_25-b06 @ Linux Firefox 7.0.1 @ Linux x86_64 Reporter: Jan Papousek The bug occurs when I start JBoss AS 7.0.2/Apache Tomcat 7.0.22 manually. The selection size validation on the page http://localhost:8080/metamer-mojarra/faces/components/richValidator/csv.... throws the following exception (this is from JBoss AS): {code} 15:45:39,631 SEVERE [org.richfaces.log.Context] (http-0.0.0.0-0.0.0.0-8080-1) Unexpected exception during isValid call: javax.validation.ValidationException: Unexpected exception during isValid call at org.hibernate.validator.engine.ConstraintTree.validateSingleConstraint(ConstraintTree.java:281) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ConstraintTree.validateConstraints(ConstraintTree.java:153) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ConstraintTree.validateConstraints(ConstraintTree.java:117) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.metadata.MetaConstraint.validateConstraint(MetaConstraint.java:84) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ValidatorImpl.validatePropertyForDefaultGroup(ValidatorImpl.java:829) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ValidatorImpl.validatePropertyForCurrentGroup(ValidatorImpl.java:742) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ValidatorImpl.validateValueInContext(ValidatorImpl.java:699) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ValidatorImpl.validateValue(ValidatorImpl.java:176) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at javax.faces.validator.BeanValidator.validate(BeanValidator.java:306) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIInput.validateValue(UIInput.java:1149) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UISelectMany.validateValue(UISelectMany.java:581) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIInput.validate(UIInput.java:967) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.1.0-20111114.102006-146.jar:] at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.1.0-20111114.102006-146.jar:] at javax.faces.component.UIForm.visitTree(UIForm.java:354) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.1.0-20111114.102006-146.jar:] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.1.0-20111114.102006-146.jar:] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.1.0-20111114.102006-146.jar:] at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:130) [richfaces-core-impl-4.1.0-20111114.102006-146.jar:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] at java.lang.Thread.run(Thread.java:662) [:1.6.0_25] Caused by: java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.util.Collection at org.hibernate.validator.constraints.impl.SizeValidatorForCollection.isValid(SizeValidatorForCollection.java:29) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] at org.hibernate.validator.engine.ConstraintTree.validateSingleConstraint(ConstraintTree.java:278) [hibernate-validator-4.2.0.Final.jar:4.2.0.Final] ... 49 more {code} It works correctly when I start a container from Eclipse Indigo (using the same profile and WAR file). -- 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

13 years

8
12
0 / 0

[JBoss JIRA] (RF-11602) RichFaces pickList buttons are rendered too narrow in smaller windows

by Karsten Wutzke (Created) (JIRA)

RichFaces pickList buttons are rendered too narrow in smaller windows --------------------------------------------------------------------- Key: RF-11602 URL: https://issues.jboss.org/browse/RF-11602 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Karsten Wutzke Priority: Minor Action buttons in a pickList are all the same size (previous bug fixed), but when making the browser window smaller the buttons are rendered much to narrow (wrong resize behavior). -- 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

13 years

7
8
0 / 0

[JBoss JIRA] (RF-11747) RF 4.1 onbeforetoggle issue

by Ibrahim Abu Ghosh (Created) (JIRA)

RF 4.1 onbeforetoggle issue --------------------------- Key: RF-11747 URL: https://issues.jboss.org/browse/RF-11747 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.1.0.CR1, 4.1.0.Milestone4, 4.1.0.Milestone3 Environment: JDK 6, JSF 2, JBoss 6 Final Reporter: Ibrahim Abu Ghosh Dears, i'am using rich:tree in two places, one in the main panel of my template, and the other one is in a popup, i'am using the onbeforetoggle event, it was running successfully since 4.0 to 4.1 M2, after M2 it is not functioning right, here is my tests : 1- RF 4-M3, onbeforetoggle not firing in the main template & in the popup. 2- RF 4-M4, main template is firing the event, popup is not firing. 3- RF 4-CR1, same as M3. here is my .xhtml code : <rich:tree id="myTree" var="node" nodeType="#{node.type}" toggleType="ajax" selectionType="ajax"> <rich:treeModelRecursiveAdaptor roots="#{bean.roots}" nodes="#{node.folders}"> <rich:treeNode title="#{node.path}" type="folder" onbeforetoggle="getSelectedPath('#{node.path}')" ondblclick="chooseFolder('#{node.ecmId}', '#{node.path}')" toggleListener="#{bean.treeToggleListener}"> <h:outputText value="#{node.label}" /> </rich:treeNode> </rich:treeModelRecursiveAdaptor> </rich:tree> where getSelectedPath is a a4j:jsFunction. -- 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

13 years

10
12
0 / 0

[JBoss JIRA] Created: (RF-10890) rich:fileUpload nothing happen when I touch add button

by Juraj Huska (JIRA)

rich:fileUpload nothing happen when I touch add button ------------------------------------------------------ Key: RF-10890 URL: https://issues.jboss.org/browse/RF-10890 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile Affects Versions: 4.0.0.Final Environment: Demo-application - richfaces-showcase-4.0.0.Final-jee6.war container - JBoss AS 6.0.0.Final mobile devices - iPhone 4 - OS version iOS 4.2.1 - browser Safari iPad1 - OS version iOS 4.2.1 - browser Safari Reporter: Juraj Huska Nothing happen when I hit the add button. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

9
13
0 / 0

[JBoss JIRA] (RF-11595) Showcase: attribute maxFilesQuantity not set

by Pavol Pitonak (Created) (JIRA)

Showcase: attribute maxFilesQuantity not set -------------------------------------------- Key: RF-11595 URL: https://issues.jboss.org/browse/RF-11595 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Reporter: Pavol Pitonak There is the following description of rich:fileUpload in Showcase but the attribute maxFilesQuantity is not set so it is possible to upload whichever number of files. {quote} This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB {quote} -- 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

13 years

9
10
0 / 0

[JBoss JIRA] (RF-11619) rich:notifyMessages in 4.1.0.M3 rf-ntf-info class not added for SEVERITY_INFO message

by Brendan Healey (Created) (JIRA)

rich:notifyMessages in 4.1.0.M3 rf-ntf-info class not added for SEVERITY_INFO message ------------------------------------------------------------------------------------- Key: RF-11619 URL: https://issues.jboss.org/browse/RF-11619 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.1.0.Milestone3 Environment: Mojarra 2.1.3, g/f 3.1.1, Windows 7, Chrome browser Reporter: Brendan Healey Thought to have been introduced in 4.1.0.M3, when a SEVERITY_INFO faces message is logged and rich:notifyMessages is in use, the notify popup is rendered as <div class="rf-ntf">, but not "rf-ntf rf-ntf-info" as expected. When a SEVERITY_ERROR is logged I see "rf-ntf rf-ntf-error", as expected. In the info scenario there is no icon in the popup. -- 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

13 years

7
7
0 / 0

[JBoss JIRA] (RF-11654) Notify: unify notification skinning based on severity with rich:message

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

Notify: unify notification skinning based on severity with rich:message ----------------------------------------------------------------------- Key: RF-11654 URL: https://issues.jboss.org/browse/RF-11654 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone3 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Minor Fix For: 4.1.0.CR1 Colors for rich:notify are currently hard-coded. Unify their skinning with rich:message. Don't forget to update documentation -- 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

13 years

5
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2011