Sine you are talking about _ah_SESSION stuff I suppose you are serializing ToBuyBeans to the sessions. On AppEngine, sessions are implemented using a combination of datastore and memecache. When you deleted your old session data from the datastore, the memcache was still there, and only when they got flushed your problem was "automatic" solved.
Sadly, I was having this trouble too previously, and the only way to get rid of it was to deploy a versions that was trying to fetch data from session and "convert" to new format or invalidate the session. This is very odd, tought, so I started to store only unchanged data, like a JSON representation of you objects, that will never stop your app when you change your code and redeploy. Gson and flex-json are good start points, apart from the fact that they add some small conversion overhead before store data in session. Hope this helps (sorry for typos ... I'm sleepy) -Ronoaldo -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/81WIdNaX5HoJ. 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.
