On 5/11/06, Johan Compagner [EMAIL PROTECTED] wrote:
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
On 5/12/06, Timothy Bennett [EMAIL PROTECTED] wrote:
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
Nevermind. I just got it working. I threw away the ResourceReference,
Wicketeers,I'm on Wicket 1.2-rc3 and I'm having some trouble invalidating a loaded resource reference. I've got a tabular list view of data that has an action panel as one of the fields in the list view. This action panel contains a link to view the tabular data in the form of a graphical chart
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.See resource.setCacheable
(boolean cacheable) and protected void configureResponse(final
