You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Claude Vedovini (JIRA)" <ji...@apache.org> on 2009/06/12 16:20:07 UTC
[jira] Created: (SLING-1004) The folder where Sling servlets store
their configuration should be configurable at deployment
The folder where Sling servlets store their configuration should be configurable at deployment
----------------------------------------------------------------------------------------------
Key: SLING-1004
URL: https://issues.apache.org/jira/browse/SLING-1004
Project: Sling
Issue Type: Improvement
Affects Versions: Launchpad Webapp 5
Reporter: Claude Vedovini
Integrating Sling as an external off-the-shelf component should be made as simple as possible, especially in web containers.
Today, when using the launchpad webapp, to configure the folder where Sling servlets will store their configuration, one as to open the war, change a file (either sling.properties or web.xml) and repack.
This is impractical for the following reasons:
- it prevents Sling webapp war to be upgraded by simply replacing the war
- it places the responsibility of the environment configuration solely on the development team whereas in some organization this is the responsibility of another team
- it does not enable easy change of the configuration to follow environmental constraints (eg. Windows/*nix)
See this mailing-list thread for further information, discussion and suggested solutions: http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200906.mbox/browser
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1004) The folder where Sling servlets
store their configuration should be configurable at deployment
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718849#action_12718849 ]
Felix Meschberger commented on SLING-1004:
------------------------------------------
Actually, the default Sling web app does *not* configure the sling.home property in the web.xml and thus uses the default which is
"sling/" + ServletContext.getContextPath().replace('/', '_')
We agreed on the list to introduce support for a new system property sling.home.prefix for the Sling web application such that the default sling.home property is defined as
System.getProperty(sling.home.prefix) + "/" + ServletContext.getContextPath().replace('/', '_')
The sling.home.prefix will only be looked up in the system properties and will only be supported by the Sling Web app. The default value of the sling.home.prefix property is "sling" for backwards compatibility.
> The folder where Sling servlets store their configuration should be configurable at deployment
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-1004
> URL: https://issues.apache.org/jira/browse/SLING-1004
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Launchpad Webapp 5
> Reporter: Claude Vedovini
>
> Integrating Sling as an external off-the-shelf component should be made as simple as possible, especially in web containers.
> Today, when using the launchpad webapp, to configure the folder where Sling servlets will store their configuration, one as to open the war, change a file (either sling.properties or web.xml) and repack.
> This is impractical for the following reasons:
> - it prevents Sling webapp war to be upgraded by simply replacing the war
> - it places the responsibility of the environment configuration solely on the development team whereas in some organization this is the responsibility of another team
> - it does not enable easy change of the configuration to follow environmental constraints (eg. Windows/*nix)
> See this mailing-list thread for further information, discussion and suggested solutions: http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200906.mbox/browser
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.