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
