ScriptedComponent has a static reference to ScriptManager which seems to stick
beyond bundle udpate
---------------------------------------------------------------------------------------------------
Key: SLING-36
URL: https://issues.apache.org/jira/browse/SLING-36
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: 2.0.0
Reporter: Felix Meschberger
Priority: Critical
Fix For: 2.0.0
The ScriptedComponent uses the ScriptManager to resolve the script to
ComponentRenderer to actually call the script. This reference is static and
obviously even survives PackageAdmin.resolveBundle() calls if the scripting
core bundle is updated.
The ScriptedComponent instances are loaded by the Core bundle and instantiated
by the Content-JCR bundle.
It has to be discovered whether this is a class loader artefact which may have
to be solved in the realm of Felix as the OSGi framework.
On the other hand, using a static reference to a class is not the best of all
solutions. A better solution trating the ScriptManager as a service must be
found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
