[
https://issues.apache.org/jira/browse/SLING-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3845.
-------------------------------------
Resolution: Duplicate
> Sling runmode cannot be changed via web.xml after first startup
> ---------------------------------------------------------------
>
> Key: SLING-3845
> URL: https://issues.apache.org/jira/browse/SLING-3845
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad Base 2.5.2
> Environment: Tomcat 6.0.39
> Reporter: Jörg Hoh
>
> When I deploy a Sling webapp (CQ 5.6.1) into a webcontainer, the init-param
> "sling.run.modes" is taken into account to setup the runmodes.
> When I change the runmode definition afterwards, the new runmodes don't show
> up at all, but the old runmodes remain. When I want to make the new runmode
> effective, I need to edit the sling.properties file to change the value there.
> One could argue, this is by intent; but I would like to have the possibility
> to change the runmodes also after the initial deployments without modifying
> directly sling-owned files, but by a more standard-like pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
