[ https://issues.apache.org/jira/browse/SLING-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-4518. ------------------------------------- Resolution: Fixed Fixed by adding a getResource before deleting > Exception when deleting a resource not managed by the root resource provider > ---------------------------------------------------------------------------- > > Key: SLING-4518 > URL: https://issues.apache.org/jira/browse/SLING-4518 > Project: Sling > Issue Type: Bug > Components: ResourceResolver > Affects Versions: Resource Resolver 1.2.2 > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Fix For: Resource Resolver 1.2.4 > > > Currently, if we register a non-jcr resource provider, and then we try to > delete content under that resource provider, we get an exception: > org.apache.sling.api.resource.PersistenceException: Unable to delete resource > at /foo/bar Resource does not exist. > at > org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.delete(JcrResourceProvider.java:613) > at > org.apache.sling.resourceresolver.impl.tree.ResourceProviderEntry.delete(ResourceProviderEntry.java:471) > at > org.apache.sling.resourceresolver.impl.ResourceResolverImpl.delete(ResourceResolverImpl.java:1106) > This is due to the changes of SLING-3973 - while the changes are necessary as > otherwise the delete operation was not always working properly, we have to > check whether a resource provider is actually providing such a resource > before deleting it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)