> 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).
Yes that is true - production reloading is a must. Our staff will create new markup and add it - while the app is running. We can't afford to restart the server each time a new markup is added. > Or did I misunderstand that? And though disabled in deployment mode by > default, he could enable it for his specific application. Possibly that could work or perhaps the idea of explicitly calling a 'clear(markup)' method on the cache might work after a new markup has been added. Perhaps it could analyse the markup to be cleared and also clear any super class markups as well. ------------------------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
