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
Yes I am a aware, but AFAIK wicket does not support controls / input fields
adjacent to forms related by the form attribute on the control.
our markup looks something like this:
...
wrote:
> The reference to the final spec:
>
>
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
