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 2017/10/16 15:44:00 UTC
[jira] [Resolved] (SLING-7201) ScriptCache implementation doesn't
correctly flush stale entries
[ https://issues.apache.org/jira/browse/SLING-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-7201.
---------------------------------
Resolution: Fixed
Fixed in [r1812299|https://svn.apache.org/r1812299].
Tests enabled through [r1812298|https://svn.apache.org/r1812298] and [r1812300|https://svn.apache.org/r1812300].
> ScriptCache implementation doesn't correctly flush stale entries
> ----------------------------------------------------------------
>
> Key: SLING-7201
> URL: https://issues.apache.org/jira/browse/SLING-7201
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Core 2.0.48
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Blocker
> Fix For: Scripting Core 2.0.50
>
>
> It seems that the changes added in SLING-6737 made the {{org.apache.sling.scripting.core.impl.ScriptCacheImpl}} to not register itself correctly as a {{org.apache.sling.api.resource.observation.ResourceChangeListener}}, since the {{ScriptEngineFactory}} references are not picked up any more by the {{bind}} / {{unbind}} methods.
> When the {{@Reference}} annotation is used in {{Component.reference()}} the {{bind}} / {{unbind}} methods have to be explicitly defined.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)