Is already in place, but not everyone checks the logs, and apparently you also didn't notice the message :)
INFO - Application - [QuickStartApplication] init: Wicket extensions initializer INFO - WebApplication - [QuickStartApplication] Started Wicket version 1.3.0-incubating-SNAPSHOT in development mode INFO - /quickstart - default: init INFO - /quickstart - jsp: init INFO - log - Started SelectChannelConnector @ 0.0.0.0:8080 Martijn On 5/30/07, Remco Bos <[EMAIL PROTECTED]> wrote:
Why not just an INFO message in the console/log? Something like: INFO - Application - [TestApplication] init: Wicket running in DEVELOPMENT mode! Kind regards, Remco Eelco Hillenius wrote: > > List, > > I'm still worried about the fact that development mode is our default > setting. Imho, this is a mistake as the development setting is a > dangerous setting for production systems: it uses more memory (for > precise line reporting), is less efficient (render check) and can > potentially bring down a server (when it runs out of file descriptors > due to resource polling). I'd much rather have a safe default than a > convenient default. > > Anyway, we've had endless discussions about this, and unfortunately I > seem to be alone having this opinion. I'd still like to do something > extra though, and Martijn mentioned a good idea, which is to have > something similar to the debug link we have for Ajax when in > development mode. If we would implement this idea, we could e.g. place > an icon that represents this (maybe combine with the Wicket logo, > wouldn't that be nice?) in the lower right corner of the browser, much > like the ajax debug link is placed right now. > > WDYT? > > Eelco > > -- View this message in context: http://www.nabble.com/development-mode-being-the-default-tf3836598.html#a10870224 Sent from the Wicket - Dev mailing list archive at Nabble.com.
-- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
