[
https://issues.apache.org/jira/browse/WICKET-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681828#comment-14681828
]
ASF subversion and git services commented on WICKET-5968:
---------------------------------------------------------
Commit 8b5a4aab78a2826c7b3ef558566be04f73632190 in wicket's branch
refs/heads/wicket-6.x from [~dashorst]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=8b5a4aa ]
WICKET-5968 CachingResourceLocator lookup key doesn't take strict into account
> CachingResourceLocator lookup key doesn't take strict into account
> ------------------------------------------------------------------
>
> Key: WICKET-5968
> URL: https://issues.apache.org/jira/browse/WICKET-5968
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.20.0, 7.0.0
> Reporter: Martijn Dashorst
> Fix For: 7.1.0
>
>
> CachingResourceLocator uses a CacheKey to store lookups for resources.
> With e.g.
> - b_nl.js
> - b.js
> When e.g. a strict resource lookup for b.js with locale "us" is performed, it
> will store the not-found for locale "us" under the cache key. The cache key
> consists of resource name, locale, style and variation. However when you
> search non-strict for locale "us", the resource locator should find the
> non-localized resource "b.js", but since a matching key for the lookup was
> stored for this particular resource, it will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
