Hi, There appears to be a bug - or at least undesired behavior - regarding cron jobs. Let's say there's a "test" and a "production" (the active) version of an app. If you add a cron job to cron.xml in "test", one would expect that job is bound to that specific version. Instead what I'm seeing:
- the cron job is listed in the GAE administrator for both apps (ie. regardless of what you select in the app version dropdown) - the cron gets invoked on "production" - and fails, as that version doesn't have the implementation For me, this is clearly a problem. The documentation does not specify how versions relate to cron jobs... however, the docs imply it's okay to run several distinct versions, even with different runtimes (ie. mixing java and python). Based on this the only reasonable approach would be to bind the cron job to the specific version of the app. One also needs this separation to be able to test the cron job's operation before going live. If running the cron job in the "test" version is not desired (eg. if the same job is already active in production), the developer should simply disable it in that version (either in cron.xml, or by detect the current version in the job implementation). Regards, Viktor -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
