if you make a resoure reference to a shared resource that is or can change.
Then you need to control the caching headers and last modified times. Else the browser will not know that it needs to refresh it.
makes sense
See resource.setCacheable (boolean cacheable) and protected void configureResponse(final Response response)
I set cachable to false to no avail. configureResponse is final, so I overrode setHeaders(), but that didn't work either. I guess I'm going to need a little sample code....
timothy
