Done: https://issues.apache.org/jira/browse/MYFACES-3880
Thanks
2014-04-10 12:16 GMT-03:00 Leonardo Uribe :
> Hi
>
> I see, now I get it. By default MyFaces always renders the view state
> field at the form end. To solve your problem, you need to render it at
> the beginning of the form.
>
> JS
Hi
I see, now I get it. By default MyFaces always renders the view state
field at the form end. To solve your problem, you need to render it at
the beginning of the form.
JSF spec javadoc for h:form says this:
"... Call ViewHandler.writeState() before the the close of the "form"
element. Render
It's necessary to have a slow internet connection to reproduce this, so I
can't test locally. While the page is loading the user hits a command
button. As the page is still loading, I guess the view state is not created
yet, so viewHandler.restoreView(facesContext, viewId) returns null.
Thanks for
Wow, you're using Shiro.
Would be nice to have a list of steps how you duplicate this in your app,
definitely and always.
I definitely suggest you use OmniFaces restore view component to avoid this
exception.
On Apr 9, 2014 1:41 PM, "Felipe Jaekel" wrote:
> I'm getting view expired exceptions
I'm getting view expired exceptions if the user tries to perform an action
in a page that isn't fully loaded.
javax.faces.application.ViewExpiredException: /page/plano/plano.jsfNo
saved view state could be found for the view identifier:
/page/plano/plano.jsf
at
org.apache.myfaces.lifecycl
5 matches
Mail list logo