this message in context:
http://www.nabble.com/-myfaces-1.2.2--session-timeout-issue-tp16627912p16627912.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
r help
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/-myfaces-1.2.2--session-timeout-issue-tp16627912p16627912.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
ion.ViewExpiredException: /result.jsfThe expected view
> was not returned for the view identifier: /result.jsf
>
> thanks for help
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/-myfaces-1.2.2--session-timeout-issue-tp16627912p16701500.html
Sent
As far as I know, MyFaces has no equivalent to the "clientStateTimeout"
setting. If client-side state-saving is used, then the state remains
valid for as long as the browser keeps it.
What kind of AJAX requests are you sending? Tomahawk sandbox PPR? Or
Trinidad PPR? Or something else?
Are you usi
gt;>> was not returned for the view identifier: /result.jsf
>>>
>>> thanks for help
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/-myfaces-1.2.2--session-timeout-issue-tp16627912p16719755.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
lt.jsf
>
> thanks for help
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/-myfaces-1.2.2--session-timeout-issue-tp16627912p16744254.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
From time to time (random on deployment or app server restart), I have
the same problem but I'm using RI jsf 1.2, trinidad 1.0.7 and facelets
1.1.13. So it looks like some kind of problem in facelets?? And yes, the
problem appears to be related with params in url. For example:
index.xhtml?somep
,
>>>
>>> I get a strange problem after migration from myfaces 1.1.5 to 1.2.2..
>>> I send an ajaw request after session timeout,
>>> I get error:
>>>
>>> javax.faces.application.ViewExpiredException: /result.jsfThe expected
>>> view
>>> wa
8 matches
Mail list logo