I have no intention of actually deploying it in development mode. I'm talking about the development sandbox provided by the Google App Engine Java SDK.
Matt Martijn Dashorst wrote: > > Never *EVER* deploy your application in development mode. Use > deployment mode and turn those features you want on. > > Martijn > > On Thu, Apr 9, 2009 at 4:33 AM, Matthew Welch <[email protected]> > 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 >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.5 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p22973951.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]
