Hei i think there is no real answer to your problem until now, is it? When i understand it right it seems that if you read data from out the session it gets deserialized an so you get a transient copy (clone) of the session data. After modifying you need to store the modified copy into the session back so that it replaces the old serialized value in the session. Is it so? That is something the google app engine developers should answer.
But i cant believe it because imho that would be a major bug in the session implementation or not? So can anybody say why the session behaves like this? This could be the reason for a strange error that i am fighting with. Thanx for any help casi --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
