Skip to content
Config.ini
The pcbeconfig.ini file is designed to hold configuration data that we don't mind customers reading, though it still requires admin permissions to access or edit. The project's long-term goal is to transition as much configuration data as possible out of the m11.cfg file and into this INI file.
To interact with the INI file, the project uses a ConfigurationManagement framework ported from PCNS, which acts as a wrapper around the Apache HierarchicalINIConfiguration class
The Apache HierarchicalINIConfiguration class actually does trigger an event when a file change is detected, but it does not broadcast this event directly to the broader PCBE application. When the framework's reload() method is called and detects an edit, the Apache framework fires a configurationChanged() event to notify any of its registered listeners. Within the PCBE system, the ConfigurationManagerImpl wrapper acts as the only listener registered directly to the Apache framework. When the Apache class detects the change and fires the event, the ConfigurationManagerImpl uses an anonymous inner class to catch it. The wrapper then calls its own fireConfigurationChange() method, which places the execution into new threads and alerts the PCBE-specific listeners (such as the GenericConfigurationListener and the ScheduledShutdownMonitorThread)
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.