Sorry, didn't mean to sound dismissive. It's a valid point, just I'm
not seeing that anybody could get to anything otherwise unavailable.
On Mon, 25 May 2020 21:02:08 +0200
Carl-Eric Menzel wrote:
> I think the point of this version decoration is not to ensure a
> particular version is requested
I think the point of this version decoration is not to ensure a
particular version is requested, because typically only one version of
a file is available in the application.
The point is instead to defeat any caching, both in the browser and by
proxies, which might serve the user an outdated vers
Hi,
Each resource in Wicket is decorated using a version string in a file
name by default. It is implemented in
FilenameWithVersionResourceCachingStrategy. Depending on DEVELOPMENT
or DEPLOYMENT mode it looks like:
jquery-ver-1590158412000.css
jquery-ver-F334A4E46CB37347CAB42E2B1A45897C.css
There
On 5/19/2020 10:08 AM, Sven Meier wrote:
Hi,
I don't understand how that exception ends up in your component
hierarchy either.
Do you use a custom exception mapper or listener? I don't see any
place in Wicket where that exception is stored.
Best regards
Sven
On 18.05.20 17:12, Calin Pav
