Are you registering your callbacks with all kinds, or with just specific kinds?
If you have sessions activated ( https://developers.google.com/appengine/docs/java/config/appconfig#Enabling_Sessions) that service generates entities to hold client data. Even task queue and cron job hits cause sessions to be generated. I believe other services also create datastore entities for management purposes. Make sure you're registering callbacks just for the kinds that need them. If you're doing that, you'll have to post source code so we can track down the problem. -Vinny P On Monday, October 15, 2012 4:48:04 PM UTC-5, sam wrote: > > I have an object that fires a callback after a put. The callback then > fires a task to do somethings. For some reason, that task then fires the > same callback again, resulting in an infinite loop. I verified that my task > is not putting that object, so the loop shouldn't be happening. Any ideas? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/jKxkihXUCjoJ. 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?hl=en.
