[
http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12459573 ]
Jukka Zitting commented on JCR-685:
---
+1, and OK for inclusion in 1.2
> Remove some synchronization on CachingNamespaceResolver
> ---
[
http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12459931 ]
Stefan Guggisberg commented on JCR-685:
---
the following methods are synchronized on the CachingNamespaceResolver
instance:
QName retrieveName(String jcrName)
S
[
http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12459960 ]
Stefan Guggisberg commented on JCR-685:
---
> How about this one?
+1
> Remove some synchronization on CachingNamespaceResolver
> -
[
http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12460069 ]
Jukka Zitting commented on JCR-685:
---
> How about this one?
-1 as it feels way too complicated, at least for 1.2.
I also don't believe that replacing synchronizati
[
http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12460192 ]
Stefan Guggisberg commented on JCR-685:
---
> I suggest to resolve this issue as currently committed, and to open a
> separate issue for improving the name resolut
[
http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12460195 ]
Jukka Zitting commented on JCR-685:
---
> i'd rather leave this issue open, the core issue (monitor contention with
> concurrent read access)
> still exists a thread d
