[appengine-java] Re: jsf view id's expire too quick
hed the same issues with mojarra 2.0.4 , so i downgraded back to mojarra 2.0.3 , and it works fine... On Jun 19, 11:46 pm, Piter Blom wrote: > Hi Mich, did you ever resolve this problem? > > I've just deployed my first app (mojarra 2.0.4) and I ran into exactly the > same problem. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: jsf view id's expire too quick
Thanks for the reply Juha. In my case changing the STATE_SAVING_METHOD from 'server' to 'client' in the web.xml already did the trick. But I will keep your suggestion in mind in case I run into problems again. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/9-VdJtBQ73sJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: jsf view id's expire too quick
Hi,
I've also seen similar errors and I'm not sure why. Using JSF 2 it happens
quite often for ajax requests. I also have another issue and I'm not sure if
it's related to the same problem. The other issue is with jsf session beans.
If you're using client-side state saving and set some value to a session
scoped jsf bean the value is not stored! I think this happens because of
some optimization to how sessions are stored. I suppose updating a session
bean (which already exists in the session) doesn't mark session dirty during
the request and doesn't trigger session saving to storage after the request
completes. I've fixed this problem by adding:
MyBean bean =
(MyBeab)FacesContext.getCurrentInstance().getExternalContext().getSession(true)).getAttribute("bean");
((HttpSession)
FacesContext.getCurrentInstance().getExternalContext().getSession(true)).setAttribute("bean",
bean);
So basically just getting the bean from session and setting it back there
fixes the problem of saving changes to session beans using client-side state
saving.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/V_x0JhPWKv4J.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: jsf view id's expire too quick
Hi Mich, did you ever resolve this problem? I've just deployed my first app (mojarra 2.0.4) and I ran into exactly the same problem. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/iGMR30Yj3NUJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
