I have also been burnt by this and I would also prefer production mode to be default. Jan
Eelco Hillenius wrote: >> IMO we should disable the shaky code that reloads templates from >> JARs (shaky not because of Wicket, but because of the JVM), and >> provide a setting to *optionally* re-activate it for the few users >> that really need this. >> > > I'm also in favor of turning this off by default, but in a slightly > different way: I'd like Wicket to operate in production mode unless > explicitly configured to operate in development mode. > > Eelco > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
