You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/12 12:39:11 UTC
[jira] [Closed] (SLING-2879) Avoid concurrency issues in a cluster
by using ResourceUtil.getOrCreateResource
[ https://issues.apache.org/jira/browse/SLING-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli closed SLING-2879.
------------------------------
> Avoid concurrency issues in a cluster by using ResourceUtil.getOrCreateResource
> -------------------------------------------------------------------------------
>
> Key: SLING-2879
> URL: https://issues.apache.org/jira/browse/SLING-2879
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Discovery Impl 1.0.0
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> org.apache.sling.discovery.impl.common.resource.ResourceHelper.getOrCreateResource/createResource use own code to create a resource. This code is not as stable/fault-tolerant as the ResourceUtil.getOrCreateResource. The latter deals with situations where the underlying repository throws stale item exceptions and such. The ResourceHelper should use ResourceUtil.getOrCreateResource and not reinvent it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)