On Sat, Mar 1, 2008 at 3:10 PM, Chris Colman <[EMAIL PROTECTED]> wrote: > I have a similar problem but it's to do with creating new markup > variations - each new one I add requires a server restart for it to be > detected. Apparently customers don't like that for some strange reason > =)
we cache the fact that variation does not exist, otherwise we would have to perform the expensive search every time. your problem can be solved by clearing the markup cache after you deploy new variations - that should work even in production mode servers. -igor > > I think your problem is easily solved - you just have to run you > production server in development mode but even in development mode my > problem is not solved. > > > > > Hi Guys, > > > > I've noticed that everytime I want to change something in my markup I > > would > > need to restart > > the server as the changes don't take effect immediately. Is there > anything > > I > > can do to avoid this behavior? > > I'm trying to adjust my css and i'm spending more time restarting the > > server... > > > > Thanks > > Carlo > > -- > > View this message in context: http://www.nabble.com/Markup-Reloading- > > tp15779009p15779009.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
