I tested my new datastore down-time period code during the scheduled down-time of a few hours ago. It failed with the same exception I reported in the link referred to above.
Does anyone know how I can disable sessions for Apache Wicket at run- time? On Jan 27, 2:17 pm, Ian Marshall <ianmarshall...@gmail.com> wrote: > I refer to the most recent post to above-named thread dated 9th > November 2010, of link > > http://groups.google.com/group/google-appengine-java/browse_thread/th... > > I can no longer post to this thread, so I start a new one here of the > same subject to post a continuation. > > For the record, I have replaced Ikai's last line of his sample code > > Capability capability = state.getCapability(); > > with > > CapabilityStatus statusDatastore = state.getStatus(); > > and then tested the condition > > (statusDatastore == CapabilityStatus.ENABLED) > > to see if the datastore is available. > > Ikai's code and my amendment tests for "Capability.DATASTORE". I use > this template to test for Capability.DATASTORE_WRITE too. I shall see > in next month's scheduled datastore down-time whether my new code will > detect this down-time and react to it cleanly. -- 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-java@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.
