January 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-5456) Non-Ajax requests badly handled if ViewExpiredExceptions are managed on client

by Pierre Wargnier (JIRA)

Non-Ajax requests badly handled if ViewExpiredExceptions are managed on client ------------------------------------------------------------------------------ Key: RF-5456 URL: https://jira.jboss.org/jira/browse/RF-5456 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: Tomcat 6 + Facelets + JSF 1.2_09 RI Reporter: Pierre Wargnier If you activate org.ajax4jsf.handleViewExpiredOnClient in web.xml, the ViewExpiredExceptions are catched by the Ajax filter and a Ajax response will create a javascript "confim" window to ask the user to reload the page. If the request that cause the ViewExpiredExceptions is not an AJAX one: only a blank page with the AJAX XML behind. Proposed solution: Handle ViewExpired on client _only_ if request is AJAX. Throw the exception the normal way otherwise. In org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(FilterChain, HttpServletRequest, HttpServletResponse) instead of log.error("Exception in the filter chain", e); if(handleViewExpiredOnClient && isViewExpired(e)){ do this: if(handleViewExpiredOnClient && isViewExpired(e) && request.getParameterMap().containsKey("AJAXREQUEST")){ log.info("View expired handling sent to client"); //View expired exceptions are quite commons, don't clog the logs tracing them -- 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

15 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (RF-5268) Editor: does not work in modalPanel

by Nick Belaevski (JIRA)

Editor: does not work in modalPanel ------------------------------------ Key: RF-5268 URL: https://jira.jboss.org/jira/browse/RF-5268 Project: RichFaces Issue Type: Bug Reporter: Nick Belaevski -- 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

15 years, 11 months

4
12
0 / 0

[JBoss JIRA] Created: (RF-4537) Inifinte Loop in org.ajax4jsf.cache.ServletContextInitMap

by David Holscher (JIRA)

Inifinte Loop in org.ajax4jsf.cache.ServletContextInitMap --------------------------------------------------------- Key: RF-4537 URL: https://jira.jboss.org/jira/browse/RF-4537 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: WebSphere 7.0 (beta) Reporter: David Holscher This code is triggered with enable-cache = true when running in WAS 7. It is an obvious infinite loop with the applicaiton has any context-params. public int size() { int result = 0; Enumeration<String> initNames = servletContext.getInitParameterNames(); while (initNames.hasMoreElements()) { result++; } return result; } -- 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

15 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-4792) Rich:orderingList throws null pointer exception while we drop some item in it, when empty

by Nik Raut (JIRA)

Rich:orderingList throws null pointer exception while we drop some item in it, when empty ----------------------------------------------------------------------------------------- Key: RF-4792 URL: https://jira.jboss.org/jira/browse/RF-4792 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: Rich:orderingList throws null pointer exception while we drop some item in it, when empty Reporter: Nik Raut Priority: Critical I have an orderingList with drop support. I drop an item in it from a table with drag support. It works fine when I already have some items in the orderingList but fails when empty. This feature used to work with RichFaces 3.2.0 version but after upgrading to 3.2.2.GA it starts throwing exception. The exception stack trace is below: Exception during request processing: Caused by javax.servlet.ServletException with message: "" javax.faces.webapp.FacesServlet.service(FacesServlet.java:277) weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223) weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243) weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003) weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909) weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) weblogic.work.ExecuteThread.run(ExecuteThread.java:181)Caused by java.lang.NullPointerException with message: "" org.richfaces.component.UIOrderingList$SubmittedValue.access$700(UIOrderingList.java:76) org.richfaces.component.UIOrderingList.validate(UIOrderingList.java:579) org.richfaces.component.UIOrderingBaseComponent.executeValidate(UIOrderingBaseComponent.java:247) org.richfaces.component.UIOrderingBaseComponent.processValidators(UIOrderingBaseComponent.java:286) org.richfaces.component.UIOrderingList.processValidators(UIOrderingList.java:330) javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1047) javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1047) javax.faces.component.UIForm.processValidators(UIForm.java:235) org.richfaces.component.UISimpleTogglePanel.processValidators(UISimpleTogglePanel.java:142) javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1047) org.richfaces.component.UISwitchablePanel.processValidators(UISwitchablePanel.java:236) org.ajax4jsf.component.AjaxViewRoot$3.invokeContextCallback(AjaxViewRoot.java:439) org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:238) org.ajax4jsf.component.AjaxViewRoot.processValidators(AjaxViewRoot.java:455) com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223) weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26) weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243) weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003) weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909) weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) weblogic.work.ExecuteThread.run(ExecuteThread.java:181) -- 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

15 years, 11 months

5
4
0 / 0

[JBoss JIRA] Created: (RF-4542) docs for web.xml settings incorrectly reference SeamFaceletViewHandler

by Ian Springer (JIRA)

docs for web.xml settings incorrectly reference SeamFaceletViewHandler ---------------------------------------------------------------------- Key: RF-4542 URL: https://jira.jboss.org/jira/browse/RF-4542 Project: RichFaces Issue Type: Bug Components: doc Reporter: Ian Springer On http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/..., the web.xml for Seam 1.2 section contains: <context-param> <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> <param-value>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</param-value> </context-param> However, it should not, since SeamFaceletViewHandler was removed from Seam as of v1.3.0 (see https://jira.jboss.org/jira/browse/JBSEAM-1367). -- 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

15 years, 11 months

5
6
0 / 0

[JBoss JIRA] Created: (RF-4810) jQuery: eval("selector}") is output

by Nick Belaevski (JIRA)

jQuery: eval("selector}") is output ----------------------------------- Key: RF-4810 URL: https://jira.jboss.org/jira/browse/RF-4810 Project: RichFaces Issue Type: Bug Reporter: Nick Belaevski <rich:jQuery query="click(function(){debugger; alert(this);addClass(this)})" selector="#table td[0] input[type='checkbox']"></rich:jQuery> Outputs eval("selector}") that's not true -- 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

15 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (RF-4459) rich:toolTip hideDelay behavior incorrect after first display

by Chris Dollar (JIRA)

rich:toolTip hideDelay behavior incorrect after first display ------------------------------------------------------------- Key: RF-4459 URL: https://jira.jboss.org/jira/browse/RF-4459 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2, 3.2.1 Environment: Ubuntu Linux 64 bit, JDK 1.5.0_09 (32 bit JDK), JBoss AS 4.2.2.GA, RichFaces 3.2.2.GA (also tested on 3.2.1.GA), Firefox2 Reporter: Chris Dollar When using a rich:tooltip with a hideDelay value set the hideDelay is only honored the first time the tooltip is rendered. After subsequent calls to show the tooltip the tooltip remains rendered on the screen. At that point you can click inside the tooltip which will cause the tooltip to be rendered again. I tested this with Richfaces 3.2.2.GA and 3.2.1.GA and got the same behavior (I've not tried it with any previous versions). I created a simple testcase based off of the tooltip demo in the main RichFaces demo. All I did was add a 'hideDelay="1000"' to both of the ajax example tooltips. Ill attach the testcase with source and a deployable .ear. -- 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

15 years, 11 months

6
11
0 / 0

[JBoss JIRA] Created: (RF-3418) default attachTiming attribute in context menu problem

by Ilya Shaikovsky (JIRA)

default attachTiming attribute in context menu problem ------------------------------------------------------ Key: RF-3418 URL: http://jira.jboss.com/jira/browse/RF-3418 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1 Reporter: Ilya Shaikovsky Assigned To: Nick Belaevski Priority: Minor If you write attachTiming="oncomplete" (I've mistaken and use this instead of onload.) - Menu will not be attached at all. attribute should handle wrong values and use default if defined wrong value. -- 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

15 years, 11 months

4
13
0 / 0

[JBoss JIRA] Created: (RF-2644) Problem with scrollableDataTable and seam link

by Rainer Flicker (JIRA)

Problem with scrollableDataTable and seam link ---------------------------------------------- Key: RF-2644 URL: http://jira.jboss.com/jira/browse/RF-2644 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: RichFaces 3.2.0.CR3 JBoss Seam 2.0.1.GA JSF 1.2 + Facelets 1.1.14 JBoss 4.2.2.GA JDK 1.5.0_11 Reporter: Rainer Flicker Seam Link with scrollableDataTable links for each item to the last item of the table. E.g. selecting item 10 of 20 opens item 20. The link shown in a browser is always the same. ------ xhtml snippet --------------------------------------------------------------------------------------------------- <rich:scrollableDataTable value="#{findings}" var="finding" height="600px" sortMode="single" width="700px"> <rich:column width="355px" sortExpression="#{finding.title}"> <f:facet name="header"> <h:outputText styleClass="headerText" value="Name" /> </f:facet> <h:outputText value="#{finding.title}" /> </rich:column> <rich:column width="60px" style="text-align:center" sortable="false"> <f:facet name="header"> <h:outputText styleClass="headerText" value="Details" /> </f:facet> <s:link action="#{findingDetailsManager.select(finding)}"> <h:graphicImage id="editimage" url="/img/buttons/edit.gif" alt="Details"></h:graphicImage> </s:link> </rich:column> </rich:scrollableDataTable> ------------------------------------------------------------------------------------------------------------------------------ -- 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

15 years, 11 months

6
13
0 / 0

[JBoss JIRA] Created: (RF-5755) extendedDataTable: onselectionchange event behavior is changed

by Svetlana mukhina (JIRA)

extendedDataTable: onselectionchange event behavior is changed -------------------------------------------------------------- Key: RF-5755 URL: https://jira.jboss.org/jira/browse/RF-5755 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.3.0 Reporter: Svetlana mukhina Assignee: Alex Tserbo Fix For: 3.3.1 Check that the current attribute description in guide corresponds its actual behavior. -- 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

15 years, 11 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2009