[ 
https://issues.apache.org/jira/browse/SLING-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-7201:
--------------------------------
    Description: 
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.

  was: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.


> 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)

Reply via email to