Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-3862

Rename of module config doesn't null of property in module instance

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Neutral
    • Resolution: Won't Do
    • Affects Version/s: 4.4.1
    • Fix Version/s: None
    • Component/s: core, modulemechanism
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            pbaerfuss Philipp Bärfuss
            Reporter:
            tmattsson Tobias Mattsson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response: