[jira] Updated: (SLING-1660) upgrade to Jackrabbit 2.1.1
[ https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1660: Attachment: System Upgrade 3.js upgrade to Jackrabbit 2.1.1 --- Key: SLING-1660 URL: https://issues.apache.org/jira/browse/SLING-1660 Project: Sling Issue Type: Improvement Components: Commons, JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Webdav 2.1.0, JCR Jackrabbit Server 2.1.0, JCR DavEx 1.0.0, Commons Testing 2.0.6 Attachments: System Upgrade 3.js -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1660) upgrade to Jackrabbit 2.1.1
[ https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1660: Attachment: Dreamweaver CS5 Update 1.js upgrade to Jackrabbit 2.1.1 --- Key: SLING-1660 URL: https://issues.apache.org/jira/browse/SLING-1660 Project: Sling Issue Type: Improvement Components: Commons, JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Webdav 2.1.0, JCR Jackrabbit Server 2.1.0, JCR DavEx 1.0.0, Commons Testing 2.0.6 Attachments: Dreamweaver CS5 Update 1.js -- 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 ] 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 ] 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-1818) [explorer] Should not be prompted to delete the root node
[ https://issues.apache.org/jira/browse/SLING-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1818: Attachment: Plugin 1.js [explorer] Should not be prompted to delete the root node - Key: SLING-1818 URL: https://issues.apache.org/jira/browse/SLING-1818 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Mike Müller Priority: Minor Fix For: Sling Explorer 1.0.0 Attachments: Plugin 1.js, screenshot0.png see screenshot. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: Plugin.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: AC_RUNACTIVECONTENT.JS, Plugin.js, SLING-1594.patch, System Upgrade 2.js SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: effects.core.min.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: AC_RUNACTIVECONTENT.JS, effects.core.min.js, Plugin.js, SLING-1594.patch, System Upgrade 2.js SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: TIc Tac Toe.dwt.asp Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: AC_RUNACTIVECONTENT.JS, effects.core.min.js, Plugin.js, SLING-1594.patch, System Upgrade 2.js, TIc Tac Toe.dwt.asp SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: AC_RUNACTIVECONTENT.JS Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: AC_RUNACTIVECONTENT.JS, SLING-1594.patch, System Upgrade 2.js SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: System Upgrade 2.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: AC_RUNACTIVECONTENT.JS, SLING-1594.patch, System Upgrade 2.js SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: Server Update.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: Server Update.js, SLING-1594.patch SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: Sytem Upgrade 1.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: Code Implement.js, SLING-1594.patch, Sytem Upgrade 1.js SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: Code Implement.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: Code Implement.js, SLING-1594.patch, Sytem Upgrade 1.js SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
