Hello,
I'm the author of the article that Daniel referred you to and I wanted to
provide some clarification on what I meant by "appears to handle" in the
comments regarding the javax.faces.STATE_SAVING_METHOD parameter in the web.xml.
Problems that I have had in the past with storing state on the server in
versions of GAE prior to 1.3 appeared to be related to the amount of time
required to persist session information to the datastore. I used to get
com.google.appengine.api.datastore.DatastoreTimeoutException exceptions using
the server option. Since the 1.3 release of GAE, I have been using server
value for this parameter in the JSF2 based applications I run on GAE. However,
none of the applications have very complicated user interfaces so the object
graph that comprises the component hierarchy is not terribly deep.
In short, for the simple applications I have written, the server parameter
works great.
The "Configuring JavaServer Faces 2.0 to run on the Google App Engine Using
Eclipse" article is getting a little long in the tooth and plan on updating it
to account for the 1.4.3 version of GAE along with the newly released JSF 2.1
reference implementation. For the most part, I think the article will not
change much aside from screen shots. The biggest change will be in the
"JavaServer Faces 2.0 and Google App Engine Compatibility Issues" article.
According to bug 1506, the JSP 2.1 compatibility issues have been resolved as
of GAE 1.4.2. As such, the section <!-- GAE Bug 1506 JSP 2.1 API but 2.0
Implementation --> of the web.xml in my sample code that talks about having to
explicitly identify the JSP expression factory implementation class may no
longer be necessary.
I hope this helps.
Derek
On Apr 5, 2011, at 5:55 AM, sgrueter wrote:
> Hello Daniel
>
> Thanks for the information.
>
> After reading the document configuring-jsf-20-to-run-on-the-google-appengine,
> the reliability of server state saving in current version
> of GAE is still not clear to me ("GAE 1.3.0 appears to handle...").
>
> <!-- ***** GAE 1.3.0 appears to handle server-side state saving. ***** -->
> <context-param>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
>
> Best regards
>
> --
> 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 [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
--
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
