[SLING-1848] registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: Scripting Core 2.0.14
• Component/s: Scripting
• Assignee: Justin Edelson
• Reporter: Justin Edelson
• Created: 20/Oct/10 19:31
• Updated: 07/Nov/10 10:43
• Resolved: 25/Oct/10 07:11

Description

ScriptEngineManagerFactory.refreshScriptEngineManager() handles the registration of an OSGi service of the ScriptEngineManager. This is used, amongst other places, by SlingScriptAdapterFactory.

However, refreshScriptEngineManager() is only called from activate() and getScriptEngineManager() (and in the latter case, only if the scriptEngineManager is null). Although bindScriptEngineManager() (and unbind) null out scriptEngineManager, they do not call refreshScriptEngineManager(). As a result, new ScriptEngineFactory services are not effective with this call sequence:

1) activate()
2) bindScriptEngineManager()
3) try adapting a script to a javax.servlet.Servlet

This can be worked around (albeit poorly IMHO) by going to the Configuration Status page in the web console because this causes getScriptEngineManager() to be called when scriptEngineManager is null, thus causing refreshScriptEngineManager() to be called.