> > This is true, but I understand Chris has a general need for > > markup reloading in production as well (though I haven't > > understood yet how Chris creates the markup files at > > runtime). Or did I misunderstand that? And though disabled in > > deployment mode by default, he could enable it for his specific > > application. > > Indeed, ModificationWatcher acting on previously not found files > should be done only in development mode by default, and Chris will > just have to enable it for his deployment.
How do I do that? Will it slow things down? Maybe the option to add a method that allows explicit clearing of the cache would be very useful because then we it can be high performance most of the time and just rebuild the cache when we indicate there is a new markup file. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
