On Thu, Jul 24, 2008 at 3:44 AM, Tormod Øverlier <[EMAIL PROTECTED]> wrote: > > When I deploy a new version of a Wicket application without restarting > Tomcat, the new version is not fully used. Java changes are applied > immediately, but html changes are not applied before I restart Tomcat. > > I have tried inserting getMarkupSettings().getMarkupCache().clear(); in the > init() method of the application, but with no luck. I've also tried stopping > the application, clearing the work directory in Tomcat and then starting the > application again, but still no luck. > > I'm using Tomcat 5.5.26 and Wicket 1.3.4. > > Why is html changes not applied unless I restart Tomcat? Could it have > something to do with Tomcat caching or class loading?
it may very well be. have you tried setting up the context with anti-jar locking enabled? -igor > -- > View this message in context: > http://www.nabble.com/Problem-when-deploying-to-Tomcat-tp18629360p18629360.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
