You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2018/10/19 15:15:00 UTC
[jira] [Resolved] (SLING-8045) The ExtensionRegistryService does
not correctly manage references
[ https://issues.apache.org/jira/browse/SLING-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-8045.
---------------------------------
Resolution: Fixed
Fixed in [commit e554fa4|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/e554fa4].
> The ExtensionRegistryService does not correctly manage references
> -----------------------------------------------------------------
>
> Key: SLING-8045
> URL: https://issues.apache.org/jira/browse/SLING-8045
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Scripting HTL Engine 1.1.0-1.4.0
>
>
> The {{org.apache.sling.scripting.sightly.impl.engine.ExtensionRegistryService}} does not correctly handle the case when a {{org.apache.sling.scripting.sightly.extension.RuntimeExtension}} is unregistered:
> 1. the {{org.apache.sling.scripting.sightly.impl.engine.ExtensionRegistryService#unbindExtensionService}} method should not require a service object;
> 2. the service should fallback to using a lower priority {{org.apache.sling.scripting.sightly.extension.RuntimeExtension}} registered for the same operation as a higher priority one, if the extension with a higher priority gets unregistered.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)