Re: [jetty-users] Hot Deployment Static Files

[Michael Gorovoy <michael@xxxxxxxxxxx>]

Andre,

Have you tried flushing the browser cache to ensure that your problem is not in the browser that cashes the response?

-Michael

On Thu, Dec 16, 2010 at 10:06 AM, Andre Ben Hamou <andre@xxxxxxxxxxxxx> wrote:

Hi all,

Apologies for the newbie question but I've gone snowblind trying to read the (somewhat sparse ;-)) docs on the deployers, the contexts, the managers and the default servlet.

I have a simple WAR that is almost all code with a tiny index page in the root. I use an atomic rsync to push new versions of the war (as root.war) up to the webapps folder on my server. Jetty hot-deploys the classes / libs flawlessly. However, the index.html update is ignored. I assumed this was because the default servlet was caching it (and failing to flush it's cache as I would expect upon a new deploy). However, setting...

  <init-param>
    <param-name>maxCacheSize</param-name>
    <param-value>0</param-value>
  </init-param>

...in webdefault.xml (which is what the instructions say to do to disable the cache) did not alleviate my problem.

So my question, quite simply, is...

How do I get the DefaultServlet to stop serving old versions of static files at the WAR root when I do a hot deploy?

Cheers,

Andre

--

...and, on the seventh day, God switched off his Mac

...and then read http://www.prfsa.com

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users