don't know then. Markup cache is as far as i know not evicted in anyway if you don't have reloading.What you could do is modify the wicket source and print a stacktrace on that info statement so that youcan see where it comes from
On 6/29/06, Marco Geier [EMAIL PROTECTED] wrote:
Well,i just
Even with DEPLOYMENT in web.xml, wicket reloads markup from time to
time. ( i didn't yet find any rules / corellations for these sporadic
reloads, but they do happen - get logged)
This doesn't happen on my WinXp based development platform, but on the
FedoraCore4 based deployment platform.
Any
if you didn't program yourself somewhere in the code that he needs to do resource pollingthen this isn't possible because then we really don't check it.Isn't it really a poll for a new resource or a new resouce for a different locale?
Or is the webapp or context not restarted suddenly somehow?If
if this: /** * @see wicket.settings.IResourceSettings#setResourcePollFrequency(wicket.util.time.Duration) */ public void setResourcePollFrequency(final Duration resourcePollFrequency)
and then:/** * @see wicket.settings.IResourceSettings#getResourceWatcher() */ public ModificationWatcher
and that shouldn't be called by yourself if possible,Just set the web.xml property or the system property to development.johanOn 6/19/06, Igor Vaynberg
[EMAIL PROTECTED] wrote:
public void init(){ configure(development, /);
}-IgorOn 6/19/06, Stefan Arentz
[EMAIL PROTECTED] wrote:
The Wiki
On 6/28/06, Johan Compagner [EMAIL PROTECTED] wrote:
and that shouldn't be called by yourself if possible,
Just set the web.xml property or the system property to development.
I've done that, but changes to the html files are still not picked up.
Not sure why :-/
S.
Using Tomcat but need to
you might have to call getresourcesettings().addresourcefoler and point it to where either your src folder with the markup files is or at some exploded packaging location.-Igor
On 6/28/06, Stefan Arentz [EMAIL PROTECTED] wrote:
On 6/28/06, Johan Compagner [EMAIL PROTECTED] wrote: and that
The Wiki contains this:
Sidenote: To see changes to template files immediatelly, overload the
init() method of the WebApplication class by specifying that you are
in development mode - remember to comment out in production:
// the second parameter is the path to your template files
//
public void init(){ configure(development, /);
}-IgorOn 6/19/06, Stefan Arentz [EMAIL PROTECTED] wrote:
The Wiki contains this:Sidenote: To see changes to template files immediatelly, overload theinit() method of the WebApplication class by specifying that you arein development mode - remember to
