Loading...
Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon
TUTORIAL

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

Google AppEngine and Serialization

Salvatore Romeo
1 decade ago Sep 02, 2010 11:07am
Henri Sara
1 decade ago Sep 02, 2010 11:21am

When using Vaadin on GAE, everything that is stored in a session needs to be serializable, including the Vaadin application state and anything referenced from it in non-transient fields etc. This is because GAE can serialize the session (including the application state) between any pair of requests, and e.g. serve the next request from another physical server.

If the Twig datastore instances and other related classes do not need to be preserved between requests, you could make them transient (or local variables in a method) and re-create them whenever necessary.

Joonas Lehtinen
1 decade ago Sep 02, 2010 1:59pm

Just to rephrase Henri - the limitation in GAE has nothing to do with Vaadin. Everything stored in GAE session must be serializable. Thus storing data layer objects in session just leads to problems (in GAE).

Toni Castelli
1 decade ago Aug 02, 2012 1:47pm
Henri Sara
1 decade ago Aug 03, 2012 6:11am
Toni Castelli
1 decade ago Aug 03, 2012 11:08am
Henri Sara
1 decade ago Aug 03, 2012 11:47am
Toni Castelli
1 decade ago Aug 03, 2012 1:09pm
Toni Castelli
1 decade ago Aug 03, 2012 6:09pm