Thanks for the note Steve. App Engine's session implementation uses memcache and the datastore, and objects must implement Serializable to be stored in either.
- Jason On Fri, Sep 11, 2009 at 11:36 AM, Steve B. <[email protected]> wrote: > > I do not know if this is a bug or if it is already documented somewhere > (I could not find this info when I searched): > > I just ran into a problem where session data worked fine in my local dev > environment, but failed when I deployed to the App Engine. > > In the AppEngine logs I found a Runtime error > "java.io.NotSerializableException". Seems that my Objects needed to > implement java.io.Serializable. > > Just thought I would pass that along in case you ran into the same > issue. It was not obvious (to me) as the log entries were only > level.warning. > > Steve B. > > > Jason (Google) wrote: > > To use sessions, you first have to enable them: > > > http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions > > > > Once sessions are enabled, you work with them the same way you work with > > sessions in other J2EE environments. > > > > - Jason > > > > On Wed, Sep 9, 2009 at 4:18 AM, zahid <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > Dear sir > > currently we are making an application host on GAE . So i have proble > > to mentain session give me any example of this > > best regard > > zahid > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
