[
https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647477#comment-14647477
]
Carsten Ziegeler commented on SLING-4895:
-----------------------------------------
[~mpetria] Yes, maybe - however I implemented equals/hashTo for mapping to just
compare the "key" part of the mapping not the value (service user name), as
this is usually used to detect duplicate mappings. A duplicate mapping is
already there if serviceName/subservicename are the same. That's why I thought
to make more drastic changes, but maybe they are not necessary
> Service registry should not be called from within synchronized block
> --------------------------------------------------------------------
>
> Key: SLING-4895
> URL: https://issues.apache.org/jira/browse/SLING-4895
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Service User Mapper 1.2.0
> Reporter: Carsten Ziegeler
> Fix For: Service User Mapper 1.2.2
>
> Attachments: SLING-4895-alt.diff, SLING-4895.diff
>
>
> RIght now, if e.g. an amendment is added/removed/updated, all
> registration/unregistration is done in a "large" synchronized block. This
> should be avoided
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
