Hi Simon, No, I wasn't aware of this application setting. I can now test without having to get up in the night to test datastore scheduled down-times! Thank you for the tip. (The same exception is thrown as during a datastore scheduled down-time.)
It remains for me to find a way to disable Apache Wicket session persistence at run-time (and not just via an uploaded configuration setting). Ian On Feb 8, 12:42 pm, Simon Knott <[email protected]> wrote: > Just as an aside, are you aware that you can disable writes to your > application via the admin console? It may make testing easier, assuming it > throws the same CapabilityDisabledException. -- 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 [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.
