[
https://jira.jboss.org/jira/browse/RF-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12421934#action_12421934
]
Alex Krasov commented on RF-3102:
---------------------------------
It seems I've found a solution for this:
After looking into a4j filter's code, I've found that the session handling is
already coded into the filter, but, for whatever reason, you need to set up a
context param to enable it.
Everything works so far, after adding the following to web.xml:
<context-param>
<param-name>org.ajax4jsf.handleViewExpiredOnClient</param-name>
<param-value>true</param-value>
</context-param>
Please confirm that this is how author intended to implement this, and close
this nasty bug if he did :)
> add Session Expired handling support in JSF 1.2 env
> ---------------------------------------------------
>
> Key: RF-3102
> URL: https://jira.jboss.org/jira/browse/RF-3102
> Project: RichFaces
> Issue Type: Feature Request
> Affects Versions: 3.2.0
> Reporter: Ilya Shaikovsky
> Assignee: Alexander Smirnov
> Fix For: 3.2.2
>
>
> currently onExpired can't be used.
> Exception thrown after session expired.
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
