November 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-7962) Dynamically generated TabPanel

by Lukas Fryc (JIRA)

Dynamically generated TabPanel ------------------------------ Key: RF-7962 URL: https://jira.jboss.org/jira/browse/RF-7962 Project: RichFaces Issue Type: Bug Components: component Affects Versions: 3.3.2.GA Environment: JBoss AS 5.1.0.GA, JDK6 Reporter: Lukas Fryc Assignee: Ilya Shaikovsky When generates rich:tabPanel dynamically using c:forEach, the model doesn't accept removing and adding again the rich:tab with the same id. Maven sample attached (dyntabpanel.tar.gz). Reproducing: 1. open application /dyntabpanel 2. let inputText as "2" 3. click Remove (the tab with "2" disappers) 4. click Add (EXCEPTION) [code] package org.richfaces.samples.dyntabpanel; import java.util.Arrays; import java.util.LinkedList; import java.util.List; public class Bean { List<String> tabs = new LinkedList<String>(Arrays.asList(new String[] {"1", "2", "3"})); String number = "2"; public String getNumber() { return number; } public void setNumber(String number) { this.number = number; } public String[] getNumberArray() { return tabs.toArray(new String[tabs.size()]); } public void remove() { if (tabs.contains(number)) { tabs.remove(number); } } public void add() { if (!tabs.contains(number)) { tabs.add(number); } } } [/code] [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:c="http://java.sun.com/jstl/core" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich"> <head> <title></title> </head> <body> <f:view> <ui:debug /> <h:form> <h:inputText value="#{bean.number}" /> <a4j:commandButton value="Add" action="#{bean.add}" reRender="numbers" /> <a4j:commandButton value="Remove" action="#{bean.remove}" reRender="numbers" /> </h:form> <rich:tabPanel switchType="ajax" id="numbers"> <c:forEach items="#{bean.numberArray}" var="number"> <rich:tab id="tab#{number}" label="#{number}" /> </c:forEach> </rich:tabPanel> </f:view> </body> </html> [/cpde] -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (RF-7980) Test-applications - spaces between columns in extended data table in IE8

by Lukas Fryc (JIRA)

Test-applications - spaces between columns in extended data table in IE8 ------------------------------------------------------------------------ Key: RF-7980 URL: https://jira.jboss.org/jira/browse/RF-7980 Project: RichFaces Issue Type: Bug Components: QA-environment Affects Versions: 3.3.1, 3.3.2.GA Environment: Apache Tomcat 6.0.20, JRE 1.6.0_16 RF 3.3.1.GA, 3.3.2.GA, 3.3.2.SR1 Reporter: Lukas Fryc Assignee: Ilya Shaikovsky Fix For: 3.3.3.CR1 Attachments: Screenshot-IE8.png The bug happens in test-applications/jsp in defualt view of ExtendedDataTable component. Screenshot attached. -- 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, 10 months

5
13
0 / 0

[JBoss JIRA] Created: (RF-7991) Exception printed in console when BeanValidator cannot be instantiated

by Bozhidar Bozhanov (JIRA)

Exception printed in console when BeanValidator cannot be instantiated ---------------------------------------------------------------------- Key: RF-7991 URL: https://jira.jboss.org/jira/browse/RF-7991 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.2.GA Reporter: Bozhidar Bozhanov Priority: Minor Below is the stacktrace - I saw it is an expected behaviour - whenever hibernate validator 4.0 (and javax.validation) are not present, then use hibernate validator 3.x. But the stacktrace, I think, should be printed, at least not on warn level. I know I can change the logging level, but still this exception doesn't tell you the exact reason for the stacktrace - which is the normal scenario of using the stable hibernate releases. 23:44:32,068 WARN ObjectValidator:56 - Bean Validator could not be instantiated java.lang.NoClassDefFoundError: javax/validation/MessageInterpolator at org.richfaces.validator.ObjectValidator.createInstance(ObjectValidator.java:54) at org.richfaces.validator.ObjectValidator.getInstance(ObjectValidator.java:85) at org.richfaces.validator.FacesBeanValidator.validate(FacesBeanValidator.java:103) at org.richfaces.component.html.HtmlInputText.validateValue(HtmlInputText.java:52) at javax.faces.component.UIInput.validate(UIInput.java:875) at javax.faces.component.UIInput.executeValidate(UIInput.java:1072) at javax.faces.component.UIInput.processValidators(UIInput.java:672) at org.ajax4jsf.component.AjaxViewRoot$3.invokeContextCallback(AjaxViewRoot.java:442) at org.ajax4jsf.component.ContextCallbackWrapper.invokeContextCallback(ContextCallbackWrapper.java:44) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:711) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675) at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:239) at org.ajax4jsf.component.AjaxViewRoot.processValidators(AjaxViewRoot.java:458) at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: javax.validation.MessageInterpolator at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 49 more -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-7453) scrollableDataTable rows are shifted to the left in case of gloab css style: body {text-align: center}

by Denis Petrunin (JIRA)

scrollableDataTable rows are shifted to the left in case of gloab css style: body {text-align: center} ------------------------------------------------------------------------------------------------------ Key: RF-7453 URL: https://jira.jboss.org/jira/browse/RF-7453 Project: RichFaces Issue Type: Bug Components: component-ScrollableDataTable Affects Versions: 3.3.1 Environment: RichFaces 3.3.1, Internet Explorer 7 Reporter: Denis Petrunin Priority: Minor scrollableDataTable rows are shifted to the left in case of gloab css style: body {text-align: center}. The issue is reproducible in IE 7. There is no such issue in IE6, FF 3.0.11. Try the following code (backing bean must return not empty list). <html xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:rich="http://richfaces.org/rich" > <head> <style type="text/css"> body {text-align: center} </style> </head> <body> <rich:scrollableDataTable value="#{bean.items}" var="item" width="200px" height="100px"> <rich:column width="70"> <f:facet name="header"> COLUMN </f:facet> #{item} </rich:column> </rich:scrollableDataTable> </body> </html> -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-8163) rich:calendar switching between JulianCalendar and Gregorian

by Thomas Morper (JIRA)

rich:calendar switching between JulianCalendar and Gregorian ------------------------------------------------------------ Key: RF-8163 URL: https://jira.jboss.org/jira/browse/RF-8163 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.2.GA, 3.3.2.CR1 Environment: Windows (several versions), Tomcat 6.0.18, MS IE 8 or Firefox 3.0. Reporter: Thomas Morper We have several rich:calendar elements at our application with date format dd-mm-yy hh:mm. We now hve the following problem: When a user types in a date without using the calendar-popup and uses a single-number year without a leading zero (e. g. 12.12.1 12:12), the calendar accepts the input (correct), but it creates a JulianCalendar for the Date cariable at the according bean, while it creates a GregorianCalendar for 12.12.01 12:12 or any other input with two digits for the year. -- 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, 10 months

4
17
0 / 0

[JBoss JIRA] Created: (RF-8119) Development: filtering

by Anton Belevich (JIRA)

Development: filtering ---------------------- Key: RF-8119 URL: https://jira.jboss.org/jira/browse/RF-8119 Project: RichFaces Issue Type: Sub-task Affects Versions: 4.0.0.ALPHA2 Reporter: Anton Belevich Assignee: Anton Belevich -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-8118) Development: sorting

by Anton Belevich (JIRA)

Development: sorting -------------------- Key: RF-8118 URL: https://jira.jboss.org/jira/browse/RF-8118 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.ALPHA2 -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-6596) InplaceSelect with Enum => Cast exception

by julien colin (JIRA)

InplaceSelect with Enum => Cast exception ----------------------------------------- Key: RF-6596 URL: https://jira.jboss.org/jira/browse/RF-6596 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Reporter: julien colin I've an Enum "Report" with these values "ALL,DELIVERED,NONE,UNDEFINED" This code with 3.2.2 it works. Code: <rich:inplaceSelect value="#{account.deliveryReport}" editEvent="onclick" selectOnEdit="true" defaultLabel="click to edit"> <s:enumItem enumValue="ALL" itemLabel="ALL" /> <s:enumItem enumValue="DELIVERED" itemLabel="DELIVERED" /> <s:enumItem enumValue="NONE" itemLabel="NONE" /> <s:enumItem enumValue="UNDEFINED" itemLabel="UNDEFINED" /> <s:convertEnum /> <a4j:support event="onviewactivated" eventsQueue="customer" action="#{entityManager.flush}" /> </rich:inplaceSelect> with 3.3.1 i have a cast exception: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Enum at org.jboss.seam.ui.converter.EnumConverter.getAsString(EnumConverter.java:56) at org.ajax4jsf.util.InputUtils.getConvertedStringValue(InputUtils.java:114) at org.richfaces.renderkit.ComboBoxBaseRenderer.getConvertedStringValue(ComboBoxBaseRenderer .java:131) at org.richfaces.renderkit.ComboBoxBaseRenderer.encodeSuggestion(ComboBoxBaseRenderer.java:1 38) at org.richfaces.renderkit.InplaceSelectBaseRenderer.encodeItems(InplaceSelectBaseRenderer.j ava:101) at org.richfaces.renderkit.html.InplaceSelectRenderer.doEncodeEnd(InplaceSelectRenderer.java :612) at org.richfaces.renderkit.html.InplaceSelectRenderer.doEncodeEnd(InplaceSelectRenderer.java :645) at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:134) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861) -- 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, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (RF-7003) comboBox: misses readonly attribute

by Ilya Shaikovsky (JIRA)

comboBox: misses readonly attribute ----------------------------------- Key: RF-7003 URL: https://jira.jboss.org/jira/browse/RF-7003 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228291#4228291 -- 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, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-8026) Selenium: create compatibility layer checking standard components' conditions

by Nick Belaevski (JIRA)

Selenium: create compatibility layer checking standard components' conditions ------------------------------------------------------------------------------ Key: RF-8026 URL: https://jira.jboss.org/jira/browse/RF-8026 Project: RichFaces Issue Type: Task Components: functional-tests, JSF 2.0 Affects Versions: 3.3.3.BETA1 Reporter: Nick Belaevski Assignee: Lukas Fryc Fix For: 3.3.3.BETA1 After upgrade from JSF 1.2 to 2.0 it appeared, that checks for standard components (e.g. existence of generated Faces messages) are not working properly due to changes in JSF renderers. I'd suggest to create separate project that will contain base check methods compatible with both JSF 1.2 and 2.0 and use it for all functional tests. It can be even covered by unit tests running Selenium tests in HtmlUnit environment (Selenium reference card from DZone refers to this as a means of tests execution speed optimization) -- 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, 10 months

2
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2009