Shared resources do set some cache headers. But a forced reload should
do a new get. Is the getResourceStream() method hit in such a case?
On 8/19/08, Boris Goldowsky <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have some pages that reference images that are in files external to
> the web application and I am serving the images via SharedResources like
> so:
>
> public class ExternalImageResource extends WebResource {
> ...
> public IResourceStream getResourceStream() {
> return new FileResourceStream(file);
> }
>
> Note I am never adding these as components to wicket pages -- I just
> have HTML that refers to the known shared-resource URLs.
>
> I am puzzled by the fact that if an image is updated on the file system,
> the application does not seem to notice this - I get the old version of
> the image until the application is shut down and restarted. It's not
> browser or network caching; shift-reload doesn't help.
>
> Am I doing something wrong, or do I need to write my own code to check
> the file system periodically for updates?
>
> Thanks
>
> Boris
>
>
> ---------------------------------------------------------------------
> 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]
