Package PamController.settings

Class SettingsNameChanger

java.lang.Object
PamController.settings.SettingsNameChanger
public class SettingsNameChanger extends Object
To improve complex module loading where settings may be saved by multiple sub-modules, in July 2015 many modules which had fixed settings had their settings names and types changed ! Therefore these modules won't have found their settings on the first go, so need to also check against the alternate names defined for each class.

It won't be possible to work out from the settingsUser.Class what changes may have been made since the class type has only recently been added to the store. Will primarily have to search on the old moduletype and perhaps run a check on type conversion and also the module name but not if it was null - indicates it would have been varying.

Mostly, the old settings had fixed types and names so can be recognised from both.

Author:
Doug Gillespie

  • Method Details

    • getInstance

      public static SettingsNameChanger getInstance()

    • findNameChange

      public SettingsNameChange findNameChange(PamSettings pamSettings)
      Find a name change. The pamSettings object will have the new type and name in it. Once this is found, then we'll be able to search for settings based on the old name.
      Parameters:
      pamSettings -
      Returns: