Hi Marios,
you're right:
ExportToolbar doesn't specify any cache information, so updates to the
data are not reflected in repeated exports.
We should improve that:
- no caching as default
- users should be able to change this easily
Can you create a Jira issue please?
Thanks
Sven
Am 12.04.19 um 11:24 schrieb mscoon:
Hi all,
We have run into some problems when using the ExportToolbar the generated
file seems to be cached in some browsers so that user's don't get a new
version if the table contents change.
I think there should be a way to tell the ExportToolbar to call
setCacheDuraction(Duration.NONE) to the ResourceStreamResource that is used
to serve the file.
There is also a related StackOverflow thread on this:
https://stackoverflow.com/questions/42602650/wicket-exporttoolbar-not-refreshing-on-table-update
We've actually run several times into caching issues with
ResourceStreamResource, and we had to explicitly set setCacheDuration to
none. I'm not sure if this is the intended behavior and if having a null
default value for ResourceStreamResource.cacheDuration is the right thing...
Thanks
Marios
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
