[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Müller updated SLING-1848: --- Attachment: (was: DreamWeaver CS5 Update.js) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: DreamWeaver CS5 Update.js registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: DreamWeaver CS5 Update.js 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: Plugin 3.js registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: Plugin 3.js 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: Plugin 3.js) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: JFrame.asp registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: HugeInteger.jsp, J Progress Bar.js, JFrame.asp, SearchForm.dwt.asp 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: J Progress Bar.js registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: HugeInteger.jsp, J Progress Bar.js, JFrame.asp, SearchForm.dwt.asp 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: HugeInteger.jsp registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: HugeInteger.jsp, J Progress Bar.js, JFrame.asp, SearchForm.dwt.asp 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: Poker.asp registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: HugeInteger.jsp, J Progress Bar.js, JFrame.asp, Poker.asp, SearchForm.dwt.asp 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: HugeInteger.jsp) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: J Progress Bar.js, JFrame.asp, Poker.asp, SearchForm.dwt.asp 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: SearchForm.dwt.asp) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: JFrame.asp) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: Poker.asp) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: J Progress Bar.js) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1848: Attachment: Plugin 2.js registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 Attachments: Plugin 2.js 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1848: - Attachment: (was: Plugin 2.js) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.14 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.