November 2007 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-1242) Tree: The 'treeNodesAdaptor' component will not properly render when a Set is passed as the 'nodes' parameter.

by Paul Hixson (JIRA)

Tree: The 'treeNodesAdaptor' component will not properly render when a Set is passed as the 'nodes' parameter. -------------------------------------------------------------------------------------------------------------- Key: RF-1242 URL: http://jira.jboss.com/jira/browse/RF-1242 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Reporter: Paul Hixson Despite the fact that the API calls for a Collection for the "nodes" parameter, the component will not render an org.hibernate.collection.PersistentSet or a java.util.Set. We are coding around this by converting the Sets returned from our database entities to java.util.List collections in special VO objects that will only be used by the one page with tree nodes. We would much prefer to use PersistentSets where the natural order of the nodes will suffice and a SortedSets for those that require a specific order, as these are out "native" Hibernate collections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

6
7
0 / 0

[JBoss JIRA] Created: (RF-1327) 3.1.3-SNAPSHOT: <rich:message> produces annoying error messages in JBoss console

by Juergen Zimmermann (JIRA)

3.1.3-SNAPSHOT: <rich:message> produces annoying error messages in JBoss console -------------------------------------------------------------------------------- Key: RF-1327 URL: http://jira.jboss.com/jira/browse/RF-1327 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.2 Environment: Eclipse 3.3.1.1, WTP 2.0.1, JBoss Tools 20071109, RichFaces 3.1.3-20071109, Facelets 1.1.14, JBoss 4.2.2, JDK 1.6.0_03 Reporter: Juergen Zimmermann When there is no error message to display then for each <rich:message> there is an error line in the JBoss console: ERROR [HtmlRichMessageRenderer] null parameter ERROR This is pretty annoying because the serious messages are not obvious any more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

7
12
0 / 0

[JBoss JIRA] Created: (RF-1371) ScrollableDataTable + a4j:support onrowclick: NOT every row can call handler if it was clicked!

by Yurii Kartsev (JIRA)

ScrollableDataTable + a4j:support onrowclick: NOT every row can call handler if it was clicked! ----------------------------------------------------------------------------------------------- Key: RF-1371 URL: http://jira.jboss.com/jira/browse/RF-1371 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.3 Environment: jdk 1.5.0 09 JBoss 4.2.0 GA JSF 1.2 + Facelets 1.1.13 RichFaces 3.1.3 SNAPSHOT MyEclipse 6.0 (as IDE and JBoss launcher) Mozilla Firefox 2.0.0.9 (as browser) Win XP SP2 as OS Reporter: Yurii Kartsev Sometimes my scrollable data table can't ordinary catch row click event and invoke its handler. Click some rows - event is invoked, click others - it isn't invoked. Detailed test and src is described on the forum(link is below). Saved HTML pages + DEBUG JBoss log - I'll try to attach it to this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

6
9
0 / 0

[JBoss JIRA] Created: (RF-1263) rich:dataTable emits "rows=" attribute to rendered HTML - breaks table.rows[] DOM access via JavaScript

by Jason Anderson (JIRA)

rich:dataTable emits "rows=" attribute to rendered HTML - breaks table.rows[] DOM access via JavaScript ------------------------------------------------------------------------------------------------------- Key: RF-1263 URL: http://jira.jboss.com/jira/browse/RF-1263 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.2 Environment: Facelets 1.1.14+Seam 2.0.0.CR3+RichFaces 3.1.2 Reporter: Jason Anderson After upgrading from RichFaces 3.1.0 to 3.1.2, some of our client side JavaScript breaks. It appears that <rich:dataTable is now emitting a "rows=nnn" attribute on the generated HTML, which breaks DOM access to table.rows[nnn] (returns undefined to JavaScript because the attribute was set in HTML as a String), table.rows[ ] must be an array. We also noticed generated DOM differences between 3.1.0 and 3.1.2 for the table header, <th> vs. <td> in header. If the rows= change happ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (RF-1438) FuncSpec-RF-OL-1.13: controls in Ordering Controls set have invalid order

by Viktor Volkov (JIRA)

FuncSpec-RF-OL-1.13: controls in Ordering Controls set have invalid order --------------------------------------------------------------------------- Key: RF-1438 URL: http://jira.jboss.com/jira/browse/RF-1438 Project: RichFaces Issue Type: Bug Components: doc Affects Versions: 3.1.3 Reporter: Viktor Volkov Assigned To: Svetlana mukhina 1. Open FuncSpec-RF-OL-1.13 Ordering List 2. Go to FuncSpec-RF-OL-CL-080-1.12 Ordering Controls set --->>> Controls in Ordering Controls set have invalid order, but labels have right order. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-1377) orderingList class = "body" adds in body e.g. <body class="body">

by Aleksej Yanul (JIRA)

orderingList class = "body" adds in body e.g. <body class="body"> ----------------------------------------------------------------- Key: RF-1377 URL: http://jira.jboss.com/jira/browse/RF-1377 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.3 Reporter: Aleksej Yanul Assigned To: Vladimir Molotkov if (window.attachEvent) {window.attachEvent("onload", init);} else {window.addEventListener("load", init, false);}document.body.onselectstart = function() {return false;}; document.body.className = "body"; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-1447) JS API of components

by Svetlana mukhina (JIRA)

JS API of components --------------------- Key: RF-1447 URL: http://jira.jboss.com/jira/browse/RF-1447 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.1.0 Reporter: Svetlana mukhina Assigned To: Korluzhenko Veronika Fix For: 3.2.0 components JS API should be reviewed and changed according to specifications -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (RF-1405) ContextMenu: disable default menu

by Nick Belaevski (JIRA)

ContextMenu: disable default menu --------------------------------- Key: RF-1405 URL: http://jira.jboss.com/jira/browse/RF-1405 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.1.3 Reporter: Nick Belaevski Assigned To: Maksim Kaszynski Fix For: 3.1.3 Add disableDefaultMenu attribute to disable native browser context menu completely if rich:contextMenu is presented somewhere on the page. "true" is default -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-1192) Calendar: time fields addition

by Nick Belaevski (JIRA)

Calendar: time fields addition ------------------------------ Key: RF-1192 URL: http://jira.jboss.com/jira/browse/RF-1192 Project: RichFaces Issue Type: Task Components: planning Affects Versions: 3.1.3 Reporter: Nick Belaevski Assigned To: Nick Belaevski Fix For: 3.1.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-1239) org.richfaces.component.state.TreeState cannot be de-serialized

by Adam Warski (JIRA)

org.richfaces.component.state.TreeState cannot be de-serialized --------------------------------------------------------------- Key: RF-1239 URL: http://jira.jboss.com/jira/browse/RF-1239 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Reporter: Adam Warski Priority: Minor When holding a TreeState in a component (Seam - either session or conversation), when the session times out and the component is removed there is an exception: 17:20:44,677 WARN [Component] Exception calling stateful session bean default @Remove method: pageT ree java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.serial.exception.SerializationExce ption: Could not create instance of org.richfaces.component.state.TreeState - org.richfaces.componen t.state.TreeState at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.postActivate(LifecycleInterceptorH andler.java:152) at org.jboss.ejb3.stateful.StatefulContainer.invokePostActivate(StatefulContainer.java:400) at org.jboss.ejb3.stateful.StatefulBeanContext.postActivate(StatefulBeanContext.java:381) at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.activateSession(Statefu lSessionFilePersistenceManager.java:316) (...) Caused by: org.jboss.serial.exception.SerializationException: Could not create instance of org.richf aces.component.state.TreeState - org.richfaces.component.state.TreeState at org.jboss.serial.classmetamodel.ClassMetaData.newInstance(ClassMetaData.java:342) at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:23 9) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreami ng(ObjectDescriptorFactory.java:412) at (...) Caused by: java.lang.InstantiationException: org.richfaces.component.state.TreeState at java.lang.Class.newInstance0(Class.java:335) at java.lang.Class.newInstance(Class.java:303) at org.jboss.serial.classmetamodel.ClassMetaData.newInstance(ClassMetaData.java:334) ... 78 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

5
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 2007