[
https://issues.apache.org/jira/browse/OAK-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808164#comment-17808164
]
Julian Reschke commented on OAK-715:
------------------------------------
There are two fundamental problems with this change.
1. It doesn't work consistenty (see OAK-10544).
2. It replaces one type of close coupling (shared map) with an even worse type
of coupling (assuming that two different layers will choose the same
replacement prefix).
> Don't share name space map between SessionImpl and LocalNameMapper
> ------------------------------------------------------------------
>
> Key: OAK-715
> URL: https://issues.apache.org/jira/browse/OAK-715
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, jcr
> Reporter: Michael Dürig
> Assignee: Marcel Reutegger
> Priority: Major
> Fix For: 0.7
>
> Attachments: OAK-715.patch
>
>
> Currently {{SessionImpl}} and {{LocalNameMaper}} share and communicate via
> the shared name space map. This is bad design and even more so since the map
> is shared across component boundaries and access to the map needs to be
> explicitly synchronized. See OAK-714.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
