[
https://issues.apache.org/jira/browse/SLING-12651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated SLING-12651:
-----------------------------------
Description:
Currently, {{resolveMapsMap}} is initialized as immutable singleton map
containing a mapping of {{GLOBAL_LIST_KEY}} to an empty list.
Later on, during alias init, it is changed to a {{ConcurrentHashMap}} and it
then immediately gets populated with a mapping for that key. For SLING-9782
this was changed to init the Map even if the ("optimized") alias init fails.
Rather than that, let's always init the map as writeable map, which also allows
to make it final (which will help with future refactorings).
was:
Currently, {{resolveMapsMap}} is initialized as immutable singleton map
containing a mapping of {{GLOBAL_LIST_KEY}} to an empty list.
Later on, during alias init, it is changed to a {{ConcurrentHashMap}} and it
then immediately get populated witjh a mapping for that key.
> ResourceResolver: avoid re-assignment of resolveMapsMap
> -------------------------------------------------------
>
> Key: SLING-12651
> URL: https://issues.apache.org/jira/browse/SLING-12651
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Trivial
>
> Currently, {{resolveMapsMap}} is initialized as immutable singleton map
> containing a mapping of {{GLOBAL_LIST_KEY}} to an empty list.
> Later on, during alias init, it is changed to a {{ConcurrentHashMap}} and it
> then immediately gets populated with a mapping for that key. For SLING-9782
> this was changed to init the Map even if the ("optimized") alias init fails.
> Rather than that, let's always init the map as writeable map, which also
> allows to make it final (which will help with future refactorings).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
