You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2021/12/21 09:17:00 UTC
[jira] [Closed] (SLING-10939) Don't register precompiled scripts that are missing
[ https://issues.apache.org/jira/browse/SLING-10939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls closed SLING-10939.
------------------------------
> Don't register precompiled scripts that are missing
> ---------------------------------------------------
>
> Key: SLING-10939
> URL: https://issues.apache.org/jira/browse/SLING-10939
> Project: Sling
> Issue Type: Bug
> Components: Scripting, Servlets
> Affects Versions: Scripting Core 2.4.0, Servlets Resolver 2.9.0
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Scripting Core 2.4.2, Servlets Resolver 2.9.2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When a bundle provides resource type capabilities for scripts that turn out to be missing an executable from the bundle (or can't be loaded) there is a case where if the resource type extends another resource type it is possible that a parent script is found.
> When the resource type wasn't based on a script in the bundle, then this should cause a registration of the parent script (and it does) - however, when it was based on a script in the bundle, it shouldn't be registered (but it is).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)