Yes that's possible, but I believe it requires you explicitly set the object on the session every time it is mutated. This more or less defeats the purpose of @SessionScoped.
There are also additional restrictions around Serialization etc. Dhanji. On Sun, Sep 5, 2010 at 12:01 AM, Andrew Wiley <[email protected]> wrote: > > > On Sat, Sep 4, 2010 at 3:13 AM, Dhanji R. Prasanna <[email protected]>wrote: > >> >> This is definitely an appengine problem. Appengine is a cluster service, >> it does not guarantee that two requests from the same user will be serviced >> by the same physical process. So anything stored in the session in the first >> request may not be available in the second. >> >> Instead of using sessions this way you must use Memcache (for data that >> can be recomputed) or the appengine datastore (for "oracular" data, i.e. >> data that cannot be recomputed). And retrieve it each time inside the >> request from either location. >> >> Dhanji. >> >> >> > I'd have to recheck the docs to be sure, but I'm pretty sure AppEngine does > guarantee that the session will carry over because it's storing the session > in the datastore under the hood. At least, that's what I remember reading. > > Andrew Wiley > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-guice%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > -- You received this message because you are subscribed to the Google Groups "google-guice" 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-guice?hl=en.
