March 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Closed: (RF-279) Sortable header

by Tsikhon Kuprevich (JIRA)

[ http://jira.jboss.com/jira/browse/RF-279?page=all ] Tsikhon Kuprevich closed RF-279. -------------------------------- Assignee: Tsikhon Kuprevich (was: Konstantin Mishin) > Sortable header > --------------- > > Key: RF-279 > URL: http://jira.jboss.com/jira/browse/RF-279 > Project: RichFaces > Issue Type: Feature Request > Components: planning > Affects Versions: 3.2.0 > Reporter: Igor Shabalov > Assigned To: Tsikhon Kuprevich > Fix For: 3.2.0 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > New component: sortable header -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-1252) rich:tree nodeSelectListener is invoked twice while used with a4j:support onselected

by Yurii (JIRA)

rich:tree nodeSelectListener is invoked twice while used with a4j:support onselected ------------------------------------------------------------------------------------ Key: RF-1252 URL: http://jira.jboss.com/jira/browse/RF-1252 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.2 Environment: JBoss 4.2.0 GA JSF 1.2 Facelets Mozilla Firefox as browser Reporter: Yurii Having rich:tree with nodeSelectListener specified, and a4j:support for event "onselected", without any actionListeners, my nodeSelectListener is invoked twice when I click on a tree node. When I remove a4j:support, everything works fine and nodeSelectListener is invoked once while I click on a node. Notice: I've tested the situation for some time and found out that nodeSelectListener is not always invoked twice. I can't find any regularity(rule), but it definitely can be invoked as twice, as once. Sometimes when I click on a node it's invoked once, sometimes - twice. But twice - is the majority. -- 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

17 years, 11 months

5
11
0 / 0

[JBoss JIRA] Closed: (RF-716) Speed up client javascripts

by Tsikhon Kuprevich (JIRA)

[ http://jira.jboss.com/jira/browse/RF-716?page=all ] Tsikhon Kuprevich closed RF-716. -------------------------------- > Speed up client javascripts > --------------------------- > > Key: RF-716 > URL: http://jira.jboss.com/jira/browse/RF-716 > Project: RichFaces > Issue Type: Feature Request > Affects Versions: 3.1.0, 3.2.0, Future Versions > Reporter: Mikhail Grushinskiy > Assigned To: Tsikhon Kuprevich > Fix For: 3.2.0 > > > Speed up client javascripts by using profiling (performance and memory), > something like direct-to-dom. Reduce memory foot print on client by destroying not needed anymore objects. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-2831) fileUpload doesn't enable the "ADD" button after file uploading

by Jim Dummy (JIRA)

fileUpload doesn't enable the "ADD" button after file uploading --------------------------------------------------------------- Key: RF-2831 URL: http://jira.jboss.com/jira/browse/RF-2831 Project: RichFaces Issue Type: Bug Environment: JBoss 3.2.2 GA, RichFaces 3.2.0.RC6, Linux, FF2 Reporter: Jim Dummy Fix For: 3.2.0 After uploading the button "ADD" stays disabled. Doesn't matter if I put immediateUpload="true" or false. The same in Opera 9, FF2, IE7 <rich:fileUpload immediate="true" fileUploadListener="#{AnySequenceForm.upload}" uploadData="#{AnySequenceForm.files}" maxFilesQuantity="1" immediateUpload="true" autoclear="true"> <a4j:support event="onuploadcomplete" ajaxSingle="true" reRender="the_sequence_panel"/> </rich:fileUpload> -- 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

17 years, 11 months

3
2
0 / 0

[JBoss JIRA] Closed: (RF-563) DataGrid ( and possible dataTable ) incorrect re-render by action from enclosed ajax component

by Viktor Volkov (JIRA)

[ http://jira.jboss.com/jira/browse/RF-563?page=all ] Viktor Volkov closed RF-563. ---------------------------- > DataGrid ( and possible dataTable ) incorrect re-render by action from enclosed ajax component > ---------------------------------------------------------------------------------------------- > > Key: RF-563 > URL: http://jira.jboss.com/jira/browse/RF-563 > Project: RichFaces > Issue Type: Bug > Reporter: Alexander Smirnov > Assigned To: Viktor Volkov > Fix For: 3.1.0 > > > On re-render table, clientId set with row key addition ( like calendarGrid:01 instead of calendarGrid ). -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-1565) Messages not updated on Ajax requests unless message tag is after the Ajax component.

by Lou Bell (JIRA)

Messages not updated on Ajax requests unless message tag is after the Ajax component. ------------------------------------------------------------------------------------- Key: RF-1565 URL: http://jira.jboss.com/jira/browse/RF-1565 Project: RichFaces Issue Type: Bug Reporter: Lou Bell One issue we've found with suggestion box that Max asked us to report, since they were found as known issues during the support case. Any messages added to the faces context are not updated on ajax requests in the suggestionbox unless the message tag is defined AFTER the suggestion box. Anything declared before it on the page fails to get updated. This is problematic for us since we usually report error messages at the top under the tab rather than below the field where it happened. See example below, a4j:outputPanel first doesn't work, but move it after the suggestion box and it functions correctly: <a4j:outputPanel ajaxRendered="true" id="componentGeneralInfoMessagesPanel"> <t:messages id="componentOverviewMessages" replaceIdWithLabel="true" tooltip="true" showDetail="true" showSummary="false" errorClass="errorText" infoClass="infoText" layout="table" /> </a4j:outputPanel> <a4j:region renderRegionOnly="false"> <h:inputText id="softwareTitle" size="35" value="#{ComponentFormController.currentRequest.name}" required="true" style="background-color: #ffffd1"> <f:attribute name="#{OSBundle['ui.validation.fieldref']}" value="Software Title" /> </h:inputText> <rich:suggestionbox for="softwareTitle" var="suggestedSoftware" suggestionAction="#{ComponentFormController.suggestSoftwareName}" frequency="0" frame="border" cellpadding="0" cellspacing="1" minChars="3" height="250" rows="100" status="loadingStatus" title="Components found in knowledgebase"> <h:column> <h:outputText value="#{suggestedSoftware}"/> </h:column> <a4j:support event="onselect" action="#{ComponentFormController.fillOnProjectSuggestion}" reRender="otherComponents,inHere" /> </rich:suggestionbox> <a4j:status id="loadingStatus"> <f:facet name="start"> <t:div id="componentSuggestWaitDiv" style="width:88%;border:3px #DAD9BB outset;background-color: #FFFFFF;"> <t:panelGrid columns="2" cellpadding="2" cellspacing="2" style="background-color: #FFFFFF;"> <h:graphicImage url="/resources/images/circle_wait.gif" /> <t:htmlTag value="h6" style="#position:relative;#top:25%"> <h:outputText style="white-space:nowrap;" value="Retrieving Results..." /> </t:htmlTag> </t:panelGrid> </t:div> </f:facet> </a4j:status> </a4j:region> -- 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

17 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-2594) Tree: IllegalArgumentException: In AbstractTreeDataModel rowIndex must be -1

by Rainer Flicker (JIRA)

Tree: IllegalArgumentException: In AbstractTreeDataModel rowIndex must be -1 ---------------------------------------------------------------------------- Key: RF-2594 URL: http://jira.jboss.com/jira/browse/RF-2594 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: JBoss Richfaces 3.2.0.CR3 JBoss Seam 2.0.1.GA JBoss AS 4.2.2.GA JDK 1.5.0_11 Reporter: Rainer Flicker Selecting a node in a richfaces tree, combined with an a4j:commandLink produces an error message. The specified action-method is never invoked. It works with Richfaces 3.2.0.CR1 and 3.1.4.GA. ------ xhtml snippet --------------------------------------------------------------------------------------------------- <rich:tree ajaxSubmitSelection="true" switchType="ajax" value="#{processTreeModel}" var="pro"> <rich:treeNode> <a4j:commandLink value="#{pro.getProcessNumber()} #{pro.getName()}" action="#{tree.nodeSelected(pro)}" bypassUpdates="true" ajaxSingle="true"> </a4j:commandLink> </rich:treeNode> </rich:tree> ------------------------------------------------------------------------------------------------------------------------------ -------- error output from JBoss AS log -------------------------------------------------------------------------- [javax.enterprise.resource.webcontainer.jsf.lifecycle] java.lang.IllegalArgumentException: In AbstractTreeDataModel rowIndex must be -1. javax.faces.FacesException: java.lang.IllegalArgumentException: In AbstractTreeDataModel rowIndex must be -1. at javax.faces.component.UIData.invokeOnComponent(UIData.java:793) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:650) at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681) at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:650) at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:236) at org.ajax4jsf.component.AjaxViewRoot.processDecodes(AjaxViewRoot.java:397) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:143) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:276) at org.ajax4jsf.Filter.doFilter(Filter.java:165) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 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:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: In AbstractTreeDataModel rowIndex must be -1. at org.richfaces.model.AbstractTreeDataModel.setRowIndex(AbstractTreeDataModel.java:50) at org.ajax4jsf.component.UIDataAdaptor.setRowIndex(UIDataAdaptor.java:302) at javax.faces.component.UIData.invokeOnComponent(UIData.java:779) ... 45 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

17 years, 11 months

3
3
0 / 0

[JBoss JIRA] Resolved: (RF-563) DataGrid ( and possible dataTable ) incorrect re-render by action from enclosed ajax component

by Viktor Volkov (JIRA)

[ http://jira.jboss.com/jira/browse/RF-563?page=all ] Viktor Volkov resolved RF-563. ------------------------------ Resolution: Rejected Assignee: Viktor Volkov (was: Nick Belaevski) > DataGrid ( and possible dataTable ) incorrect re-render by action from enclosed ajax component > ---------------------------------------------------------------------------------------------- > > Key: RF-563 > URL: http://jira.jboss.com/jira/browse/RF-563 > Project: RichFaces > Issue Type: Bug > Reporter: Alexander Smirnov > Assigned To: Viktor Volkov > Fix For: 3.1.0 > > > On re-render table, clientId set with row key addition ( like calendarGrid:01 instead of calendarGrid ). -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (RF-767) Tooltip: in "ajax" mode opens and closes immediately

by Mikhail Vitenkov (JIRA)

[ http://jira.jboss.com/jira/browse/RF-767?page=all ] Mikhail Vitenkov closed RF-767. ------------------------------- > Tooltip: in "ajax" mode opens and closes immediately > ----------------------------------------------------- > > Key: RF-767 > URL: http://jira.jboss.com/jira/browse/RF-767 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.1.0, 3.2.0 > Reporter: Nick Belaevski > Assigned To: Mikhail Vitenkov > Priority: Critical > Fix For: 3.1.0, 3.2.0 > > -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-2260) jsf-facelets.jar locked by RF (org.ajax4jsf.Filter?)

by Juergen Zimmermann (JIRA)

jsf-facelets.jar locked by RF (org.ajax4jsf.Filter?) ---------------------------------------------------- Key: RF-2260 URL: http://jira.jboss.com/jira/browse/RF-2260 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5 Environment: RF 3.1.4SR1, JBossAS 4.2.2, JDK 1.6.0_04, Facelets 1.1.14, JBoss Tools nightly 20080201, WinXP SP2 Reporter: Juergen Zimmermann When undeploying an EAR archive from JBossAS, then until RF 3.1.4 these two JARs couldn't be deleted inside the deploy directory of JBoss: a) richfaces-impl-3.1.4.GA.jar and b) richfaces-ui-3.1.4.GA.jar Upgrading to RF 3.1.4SR1 these 2 JARs now can be deleted. However, now jsf-facelets.jar cannot be deleted although this could be deleted in 3.1.4, 3.1.3, ... There seems to be an issue regarding resource locking of org.ajax4jsf.Filter and the web.xml context parameter: <context-param> <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> <param-value>com.sun.facelets.FaceletViewHandler</param-value> </context-param> Please see also http://jira.jboss.com/jira/browse/RF-1284 -- 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

17 years, 11 months

4
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 March 2008