Rename of module config doesn't null of property in module instance
-------------------------------------------------------------------
Key: MAGNOLIA-3862
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3862
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: core, modulemechanism
Affects Versions: 4.4.1
Reporter: Tobias Mattsson
Assignee: Philipp Bärfuss
Split off from MAGNOLIA-3457.
If I have the config loaded and rename a property, the module is reloaded but
the property is still there with all old values. I think it should be null.
Renaming property.
2010-12-08 12:21:25,599 INFO AdminTreeMVCHandler.renameNode(564)
Moving node from /modules/kokaihop/config/properties to
/modules/kokaihop/config/properties2
2010-12-08 12:21:30,609 INFO ModuleManagerImpl.stopModule(388)
Stopping module kokaihop
2010-12-08 12:21:30,609 INFO KokaihopModule.stop(60)
module stop, during restart
2010-12-08 12:21:30,610 INFO ModuleManagerImpl.startModule(380)
Starting module kokaihop
2010-12-08 12:21:30,610 INFO KokaihopModule.start(49)
module start, during restart
Module restarted but property is still intact.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
