-
1. Re: how to handle ViewExpiredException?
lmk Apr 16, 2008 4:52 AM (in response to lmk)Hi.
I can't also use A4J.AJAX.onExpired after upgrading to RF 3.2.0 and myfaces 1.2.2A4J.AJAX.onExpired = function(loc,expiredMsg){ // Custom Developer Code };
my environement:
RF 3.2.0,facelets 1.1.14,myfaces 1.2.2,tomcat 5.5.23
thanks/ -
2. Re: how to handle ViewExpiredException?
lmk Apr 16, 2008 9:44 AM (in response to lmk)
it seems that the exception is handled on FacesServlet, after thrown by AjaxViewHandler restore view.
what I have to do to turn round this problem.? -
3. Re: how to handle ViewExpiredException?
lmk Apr 16, 2008 11:53 AM (in response to lmk)no body care :( !!
-
4. Re: how to handle ViewExpiredException?
ilya_shaikovsky Apr 16, 2008 12:41 PM (in response to lmk)add
com.sun.faces.enableRestoreView11Compatibility=true
context param to your web.xml
onExpired should works after -
5. Re: how to handle ViewExpiredException?
ilya_shaikovsky Apr 16, 2008 12:55 PM (in response to lmk)Anyway it's just a workaround. Issue added:
http://jira.jboss.com/jira/browse/RF-3102 -
-
7. Re: how to handle ViewExpiredException?
alex_krasov Jul 19, 2008 8:42 AM (in response to lmk)Use richfaces 3.2.1 and set context param org.ajax4jsf.handleViewExpiredOnClient=true at web.xml
This shall fix the issue without setting restore view to 1.1 compatability mode...
Cheers. -
8. Re: how to handle ViewExpiredException?
user080701 Jul 19, 2008 9:36 AM (in response to lmk)1:
add
com.sun.faces.enableRestoreView11Compatibility=true
context param to your web.xml
2.
set context param org.ajax4jsf.handleViewExpiredOnClient=true at web.xml
Which one is better? -
9. Re: how to handle ViewExpiredException?
alex_krasov Jul 19, 2008 3:23 PM (in response to lmk)Probably the 2nd approach.
This way you've got a default JSF1.2 restore view behaviour and working richfaces onExpired support...