September 2008 - richfaces-issues

[JBoss JIRA] Created: (RF-4336) Effect, Insert: troubles 'View Source' link in richfaces-demo.

by Alexander Dubovsky (JIRA)

Effect, Insert: troubles 'View Source' link in richfaces-demo. -------------------------------------------------------------- Key: RF-4336 URL: https://jira.jboss.org/jira/browse/RF-4336 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: richfaces-demo, 3.2.2.CR1 Reporter: Alexander Dubovsky Assignee: Ilya Shaikovsky Priority: Minor Attachments: 13 - for Opera.png # Open any page in rich-faces-demo # Click 'View Source' link and then 'Hide' link before code appearing. Result for Opera 9.52: see screen shot. Result for all other browsers: vertical scroll appears after expanding source again. See screen shot. -- 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, 7 months

4
18
0 / 0

[JBoss JIRA] Created: (RF-4001) calendar: disabled="true" and popupMode="false" => calendar is enabled

by Tatyana Romanovich (JIRA)

calendar: disabled="true" and popupMode="false" => calendar is enabled ---------------------------------------------------------------------- Key: RF-4001 URL: https://jira.jboss.org/jira/browse/RF-4001 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RF-3.2.2.BETA2 jsp, facelets test-application Tomcat 6 all browsers Reporter: Tatyana Romanovich Assignee: Nick Belaevski 1. Go to the test application and select calendar component 2. Set disabled="true" and popupMode="false" 3. Verify state of calendar FAILURE: it's enabled (BUG) NOTE: disabled attribute works only for popup mode -- 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, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-4268) demo site: inplaceInput: Save and Canxel buttons don't work

by Tatyana Romanovich (JIRA)

demo site: inplaceInput: Save and Canxel buttons don't work ----------------------------------------------------------- Key: RF-4268 URL: https://jira.jboss.org/jira/browse/RF-4268 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RF-3.2.2.BETA5 any browser Reporter: Tatyana Romanovich Assignee: Nick Belaevski Priority: Critical 1. Go to the demo site 2. Select inplaceInput component 3. In the third example enter any value and click Save or Cancel button FAILURE: inplaceInput component has "Editable" state. -- 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, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (RF-4271) demo site: inplaceSeletc: save and cancel buttons work incorrectly

by Tatyana Romanovich (JIRA)

demo site: inplaceSeletc: save and cancel buttons work incorrectly ------------------------------------------------------------------ Key: RF-4271 URL: https://jira.jboss.org/jira/browse/RF-4271 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RF-3.2.2.BETA5 all browsers Reporter: Tatyana Romanovich Assignee: Vladimir Molotkov Priority: Critical 1. Go to the inplaseSelect page (demo site) 2. Find last example (using controls facet) 3. Expand list of values, select any value, click Save or Cancel button FAILURE: list of values is displayed yet 4. Click on the other control FAILURE: it's impossible, page is blocked by expanded inplaceSelect control. -- 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, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (RF-4486) Develop Selenium tests for rcih:graphValidator

by Nick Belaevski (JIRA)

Develop Selenium tests for rcih:graphValidator ---------------------------------------------- Key: RF-4486 URL: https://jira.jboss.org/jira/browse/RF-4486 Project: RichFaces Issue Type: Task Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Vladimir Molotkov Fix For: 3.3.0 -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-4485) Develop Selenium tests for rich:beanValidator

by Nick Belaevski (JIRA)

Develop Selenium tests for rich:beanValidator --------------------------------------------- Key: RF-4485 URL: https://jira.jboss.org/jira/browse/RF-4485 Project: RichFaces Issue Type: Task Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Vladimir Molotkov Fix For: 3.3.0 -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-4484) Develop Selenium tests for rcih:ajaxValidator

by Nick Belaevski (JIRA)

Develop Selenium tests for rcih:ajaxValidator --------------------------------------------- Key: RF-4484 URL: https://jira.jboss.org/jira/browse/RF-4484 Project: RichFaces Issue Type: Task Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Vladimir Molotkov Fix For: 3.3.0 -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-4399) Create selenium test

by Nick Belaevski (JIRA)

Create selenium test -------------------- Key: RF-4399 URL: https://jira.jboss.org/jira/browse/RF-4399 Project: RichFaces Issue Type: Sub-task Affects Versions: 3.2.2 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 3.3.0 -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-4411) ViewExpiredException when transferred to error page declared in web.xml

by Fabien Gaujous (JIRA)

ViewExpiredException when transferred to error page declared in web.xml ----------------------------------------------------------------------- Key: RF-4411 URL: https://jira.jboss.org/jira/browse/RF-4411 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Environment: RichFaces 3.1.4 GA, MyFaces 1.2.2, Facelets 1.1.14, Tomcat 6 Reporter: Fabien Gaujous Hello, When a backing bean throws an Exception (HibernateException in our case), instead of being redirected to the error page declared in web.xml, we end up with the default Tomcat 500 error page. This is due to a a ViewExpiredException that is triggered while the system attempts to perform the Restore View JSF phase for the page with view id "/500.xhtml". Here is the stack trace from the Tomcat log: 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:844) 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:613) Sep 5, 2008 4:58:00 PM org.apache.catalina.core.ApplicationDispatcher invoke SEVERE: Servlet.service() for servlet HWFacesServlet threw exception javax.faces.application.ViewExpiredException: /500.xhtmlThe expected view was not returned for the view identifier: /500.xhtml at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:88) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:438) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343) at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:287) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) 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:844) 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:613) Sep 5, 2008 4:58:00 PM org.apache.catalina.core.StandardHostValve custom SEVERE: Exception Processing ErrorPage[errorCode=500, location=/faces/500.xhtml] javax.servlet.ServletException: /500.xhtmlThe expected view was not returned for the view identifier: /500.xhtml at javax.faces.webapp._ErrorPageWriter.throwException(_ErrorPageWriter.java:401) at javax.faces.webapp.FacesServlet.handleLifecycleException(FacesServlet.java:221) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:156) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:438) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343) at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:287) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) 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:844) 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:613) Caused by: javax.faces.application.ViewExpiredException: /500.xhtmlThe expected view was not returned for the view identifier: /500.xhtml at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:88) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148) ... 17 more Our web.xml is as follows: <?xml version="1.0" encoding="ISO-8859-1"?> <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4"> <display-name>App</display-name> <context-param> <param-name>facelets.VIEW_MAPPINGS</param-name> <param-value>*.xhtml</param-value> </context-param> <context-param> <param-name>facelets.LIBRARIES</param-name> <param-value>/WEB-INF/tags/kpu/kpu.taglib.xml</param-value> </context-param> <context-param> <param-name>facelets.DEVELOPMENT</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>facelets.REFRESH_PERIOD</param-name> <param-value>-1</param-value> </context-param> <context-param> <param-name>facelets.SKIP_COMMENTS</param-name> <param-value>false</param-value> </context-param> <context-param> <description>http://wiki.apache.org/myfaces/RedirectTracker</description> <param-name>org.apache.myfaces.redirectTracker.POLICY</param-name> <param-value>org.apache.myfaces.custom.redirectTracker.policy.FullRedirectTrackPolicy</param-value> </context-param> <context-param> <param-name>org.apache.myfaces.RENDER_VIEWSTATE_ID</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>org.apache.myfaces.ERROR_HANDLING</param-name> <param-value>false</param-value> </context-param> <listener> <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class> </listener> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> <listener> <listener-class>org.springframework.web.context.request.RequestContextListener</listener-class> </listener> <filter> <description>This filter is the Ajax4JSF</description> <display-name>Ajax4jsf Filter</display-name> <filter-name>ajax4jsf</filter-name> <filter-class>org.ajax4jsf.Filter</filter-class> </filter> <filter> <description>This is the MyFaces extension</description> <filter-name>extensionsFilter</filter-name> <filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class> <init-param> <param-name>uploadMaxFileSize</param-name> <param-value>500k</param-value> </init-param> <init-param> <param-name>uploadThresholdSize</param-name> <param-value>1k</param-value> </init-param> </filter> <filter-mapping> <filter-name>extensionsFilter</filter-name> <url-pattern>/faces/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>extensionsFilter</filter-name> <servlet-name>HWFacesServlet</servlet-name> </filter-mapping> <filter-mapping> <filter-name>ajax4jsf</filter-name> <servlet-name>HWFacesServlet</servlet-name> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> </filter-mapping> <servlet> <servlet-name>HWFacesServlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>2</load-on-startup> </servlet> <servlet-mapping> <servlet-name>HWFacesServlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping>  <error-page> <error-code>500</error-code> <location>/faces/500.xhtml</location> </error-page> </web-app> Here is what we found from our investigation. When submitting a login form from page "/login.xhtml", our code triggers a HibernateException. This generates a 500 error. Then, in org.apache.myfaces.lifecycle.RestoreViewExecutor#execute, when reaching the Restore View JSF phase for view id "/500.xhtml", restoreViewSupport.isPostback(facesContext) is true, and thus, thinking this is a postback situation (which is weird as we are moving to a different page, the error one), the system attempts to restore a viewroot using the current view state. The problem is, there is no existing view state in the session for view id "/500.xhtml" -- there is only state for the page we are coming from and which triggered the HibernateException, "/login.xhtml" (the view state is searched / computed in org.ajax4jsf.application.AjaxStateManager#restoreView). So the viewRoot returned by viewHandler.restoreView(facesContext, viewId) is null, and a ViewExpiredException is thrown. The default Tomcat error page is then shown. // Determine if this request is a postback or initial request if (restoreViewSupport.isPostback(facesContext)) { if (log.isTraceEnabled()) log.trace("Request is a postback"); viewRoot = viewHandler.restoreView(facesContext, viewId); if (viewRoot == null) { throw new ViewExpiredException("The expected view was not returned " + "for the view identifier: " + viewId, viewId); } restoreViewSupport.processComponentBinding(facesContext, viewRoot); } else { ... } -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-4445) Javascript-Error, when loading of HTML-page interrupted in IE 6

by Alexey Shakov (JIRA)

Javascript-Error, when loading of HTML-page interrupted in IE 6 --------------------------------------------------------------- Key: RF-4445 URL: https://jira.jboss.org/jira/browse/RF-4445 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: Server: Tomcat 6.0.13, myfaces 1.2.2, facelets Client: WinXP, IE6.0 Reporter: Alexey Shakov Each HTML-page in my App includes customer JS. This JS checks, if the current HTML-page is loaded inside a frameset (customer portal). If not, then follows the redirect to this frameset and the current HTML-page is shown inside this frameset. JS-Error (in some of a4j-JS) occurs during redirect. -- 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, 7 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2008