Implement centralized preference default loading strategy
Some preferences are loaded at Taxeditor startup before any connection to a CDM data source was made. Since some preferences now include the active CDM store in their keys, they may not be used correctly.
One case where this may be the problem:
- When starting the Taxeditor with local and DB preferences cleared, all search options are disabled.
#1 Updated by Katja Luther over 2 years ago
- Status changed from New to In Progress
- Target version changed from Unassigned CDM tickets to Release 5.5
The initialization of the preferences is already moved to contextStart in LifeCycleManager, so the cdm data store is available. But the initialization of the search configuration is done, when the SearchBar is created, this is before the editor is connected to a cdm instance.
Now the search configuration is done for an editor instance not the db instance, we have to decide whether this is the wanted behaviour or the users want to define the search options for every cdm instance.
#10 Updated by Andreas Müller about 2 years ago
Andreas Müller wrote:
In DistrEd when having status defined in DBPrefs without allow override after restart of TaxEditor (and CDM Server, relevant?) it shows the complete status list, not only those selected in DBPrefs!!
Only if allow override is selected the correct status list is shown.