viewexpiredexception

问题 Mojarra Implementation of JSF 2 has the following context params: com.sun.faces.numberOfViewsInSession (default is 15) com.sun.faces.numberOfLogicalViews (default is 15) What is the difference between them? The documentation doesn't speak much about these. My app was having trouble with ViewExpiredException for some pages, but after we bumped these settings to a (much) higher value, we stopped having problems. My app is a financial, form-heavy, ajax-enabled app (some screens have 50+ inputs,

问题 I've read the question Handle ViewExireException/ajax and display a Primefaces dialog and the answer from BalusC. I'd want to handle the ViewExpiredException by showing the alert with information to refresh the page. I've taken the suggestion from BalusC to user RequestContext to put JavaScript to execute, and I've removed the JSF redirection because I'm not using it: @Override public void handle() throws FacesException { for (Iterator<ExceptionQueuedEvent> i =

问题 I set up my web app as follows: <error-page> <exception-type>javax.faces.application.ViewExpiredException</exception-type> <location>/WEB-INF/include/viewExpired.html</location> </error-page> so that the above error page be displayed when the viewExpiredException is thrown. However, when I restart the server and submit an ajax request on an "left-open" page, the exception is thrown in the console and my error page is not displayed. Here is that stack trace from the console: javax.faces

问题 I have a JSF application that uses Mojarra 2.2.9 and is deployed on WebSphere 8.5.5.4 on clustered environement and javax.faces.STATE_SAVING_METHOD is set to client . Even though all my application beans are request scoped, sometimes when the user session is valid and the user is doing post request on a page he gets ViewExpiredException . What may be causing this issue and how can I solve it? Will changing the javax.faces.STATE_SAVING_METHOD to server solve it? If so, what is the impact of

问题 after upgrading to JBoss AS 7, suddenly the POST request of the first login page of our application results in a ViewExpiredException. Everything worked fine under JBoss AS 6. Since the classloading is way nicer in AS 7, I put some dependencies from the "server/default/lib" folder into the Maven dependencies to deploy them with the application (WAR/EJB-JAR packed as EAR). I also added the directive to alter the classpath in MANIFEST.MF. Thus, every library is found. However, modules that are

问题 I have a question : When jsf view has expired, can we be sure that the session is destroyed and all its attributes are removed ? Thank you for responding me. 回答1: No. It's the other way round, provided that javax.faces.STATE_SAVING_METHOD is set to its default value of server . Then a session destroy indeed implies an expireation of all views saved so far in the session. If the state saving is however set to client , then the view never expires. See also: javax.faces.application

问题 I'm attempting to migrate an existing JSF application from JSF 1.2 to JSF 2.0. I was using MyFaces 1.2.8 and want to use MyFaces 2.0.5. What I'm experiencing with MyFaces 2.0.5 is that the initially requested page will render properly, but any attempt to navigate to another page will result in a ViewExpiredException . The message is: No saved view state could be found for the view identifier: /SomePageName.jsf (where "SomePageName" is the name of the page that I am navigating away from) If I

问题 I have an application using JSF1.2 + Richfaces 3.3.3 Final, MyFaces 1.2.7, Spring + Hibernate and I get the below exception everytime when I clear the cache and cookies of the browser and login again to my application. javax.faces.application.ViewExpiredException - /app/project/index.jsf No saved view state could be found for the view identifier: /app/project/index.jsf Can anyone let me know how to solve above exception? 回答1: You can solve it by setting the state saving method to client

问题 I've put the following into my web.xml: <error-page> <exception-type>javax.faces.application.ViewExpiredException</exception-type> <location>/expiredIndex.jsf</location> </error-page> <error-page> <exception-type>java.lang.Throwable</exception-type> <location>/error.jsf</location> </error-page> <session-config> <session-timeout>1</session-timeout> </session-config> When I start my app, and wait for 1 minute, if I then attempt to interact with it (JSF 1.2, h:commandButton ) I get the error

问题 I have a page that has the setup as below with url like my.page.com/table.xhtml?id=123 : +----------------------------------------------+ |Meta information | |----------------------------------------------| | Search Fields Submit btn | |----------------------------------------------| | | | | | Big p:dataTable | | with rowExpansion | | | |----------------------------------------------| | Pager | +----------------------------------------------+ id=123 is the request parameter that controls the