[
https://issues.apache.org/jira/browse/TRINIDAD-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569034#action_12569034
]
Scott O'Bryan commented on TRINIDAD-943:
----------------------------------------
I thought trinidad already had a usecase for this. In either case, yes, a
configurator would be the right way to handle this although, in a portlet
environment, session timeouts are largely irrelevant. The portlet handles the
request and if the portlet's session has timed out, our portlet may not even
get the request. For the full page case, this would be fine. For the PPR
case, it may hose us.
In any case, what I would do in the portal case is, if we do get the request, I
would either treat it like we have not timeout_url OR I would simply write out
the redirect url to be the current action url. This will "try" to post an
action request to the portlet, but then the portal will take over and prompt
the user for sign in.
I have some code for a configuator which does something similar that I can
forward you.
Scott
> handle session timeout
> ----------------------
>
> Key: TRINIDAD-943
> URL: https://issues.apache.org/jira/browse/TRINIDAD-943
> Project: MyFaces Trinidad
> Issue Type: New Feature
> Reporter: Matthias Weßendorf
> Assignee: Matthias Weßendorf
> Priority: Minor
>
> provide solution to handle session timeouts
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
