This way you won't get no exceptions any more, but it's also terrible to develop without ModificationWatching. GAE does not allow spawning threads even in the local development environment.
I tried to use my own implementation of a modification watcher, that does not spawn any threads but instead it does the modification watching before every request. Unfortunately it's not possible to replace the default ModificationWatcher in Wicket, because it's got dependencies to the concrete default ModificationWatcher and that is final, so you can't replace it with another implementation. You can work around this by doing some classpath messing and put your own ModificationWatcher implementation in your project into same package org.apache.wicket.util.watch of the Wicket ModificationWatcher see http://kimenye.blogspot.com/2009/06/google-app-engine-wicket.html here . Would be nice if Wicket relied on an interface IModificationWatcher in future versions, so that it can be replaced by a customized version. Or don't make it final. - cretzel Jonathan Locke wrote: > > > not sure, but try getResourceSettings().setResourcePollFrequency(null) in > your app init > > > Matt Welch wrote: >> >> I'm experimenting with Wicket inside Google's new Java support for its >> App >> Engine. My simple apps run fine if the configuration is set to >> DEPLOYMENT, >> however in development mode, I get an exception related to >> ModificationWatcher. Looking at the exception I think this >> ModificationWatcher is being used as part of a new thread which is a >> no-no >> inside the App Engine sandbox. Is there way way to just disbable this >> modification watcher without putting the entire app in deployment mode? >> There are a number of items I like about development mode but this one >> glitch is preventing me from using it. >> >> Matt >> >> > > -- View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p24099680.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
