What is the best way to deal with objects that still get cached when a transaction fails and is rolled back?
-- I am running into this with GAE / JDO / GWT RequestFactory. The transaction rightfully fails and rolls back, but then the memcache still retains the older values. The datastore has the correct values, but then memcache does not.
This can also lead to others issues when, for example, if a new object were persisted during the transaction. Again the object is cached, however because the transaction failed, it is actually not in the datastore resulting in a NucleusOptimisticException: "The underlying entity had already been deleted." exception.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment