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 the
And 1 more thing , the error got fixed by itself, after several hours,
the "previously-existing ToBuyBean persistent entities" were somehow
deleted (not by me)...
so how can i do it by myself if i want to?
Thanks ahead
On Oct 29, 10:20 pm, Daniel wrote:
> The ToBuyBean class indeed implements S
The ToBuyBean class indeed implements Serializable , (but its not
stored or persisted in the DB)
How can I get rid of "previously-existing ToBuyBean persistent
entities?"
On Oct 28, 10:14 am, Ian Marshall wrote:
> If you are getting this exception when running on the GAE/J cloud,
> have you del
I somehow managed to persist an List to the datastore [declaring other
ArrayList and then using it on setter, it somehow did not want to just
store my list when passed to a setter]. But it does not work that way
for removing items from the list.
I need a runnable block to run it in the transaction
Hi there,
Until recently I had a happily working app with one mail handler and Spring
MVC configured in web.xml as follows:
imageMailHandler
/_ah/mail/*
springMvc
/
Today I added a second mail handler, so I had to make the url pattern for
both mail handlers more specific:
yahooGroupsMail
