[
https://issues.apache.org/jira/browse/WICKET-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840113#comment-17840113
]
Alexander Ermer commented on WICKET-7106:
-----------------------------------------
Thanks for this suggestion. For me this will do the trick, by fixing the
version for caching to 1000-final
{code:java}
getResourceSettings().setCachingStrategy(new
FilenameWithVersionResourceCachingStrategy(new
StaticResourceVersion("1000-final"))); {code}
This will be removed when we use the next Wicket version.
> Changes in JS File between milestone and final release are cached by browsers
> -----------------------------------------------------------------------------
>
> Key: WICKET-7106
> URL: https://issues.apache.org/jira/browse/WICKET-7106
> Project: Wicket
> Issue Type: Wish
> Affects Versions: 10.0.0
> Reporter: Alexander Ermer
> Priority: Trivial
>
> My issue is the latest change of wicket-ajax-jquery.js between 10.0.0-M2 and
> 10.0.0 (final) from
> https://github.com/apache/wicket/commit/653d31b1154450626fc8c4047a6b25007924bf90
>
> We had to go in production with the milestone version which serves the file
> wicket-ajax-jquery-ver-1000.js. The exakt same filename is served by the
> final releaes BUT there are changes. Default browser settings do cache these
> files which leads to undefined function calls of `Wicket.Event.requestSubmit`.
>
> This issue is very easy to solve: please just release a version like 10.0.1
> without any changes. That way the file wicket-ajax-jquery-ver-1001.js would
> be served and my problems are gone.
>
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
