Package jmri.jmrix.openlcb.configurexml
Class OlcbEventNameStoreXml
java.lang.Object
jmri.jmrit.XmlFile
jmri.jmrix.openlcb.configurexml.OlcbEventNameStoreXml
JMRI's implementation of part of the OpenLcb EventNameStore interface persistance
-
Nested Class Summary
Nested classes/interfaces inherited from class jmri.jmrit.XmlFile
XmlFile.Validate -
Field Summary
FieldsFields inherited from class jmri.jmrit.XmlFile
dtdLocation, xsltLocation -
Constructor Summary
Constructors -
Method Summary
Methods inherited from class jmri.jmrit.XmlFile
addDefaultInfo, backupFileName, checkFile, createFileNameWithDate, dumpElement, findFile, getBuilder, getDefaultDtdLocation, getDefaultValidate, getDtdLocation, getProcessingInstructionHRef, getProcessingInstructionType, getRoot, getValidate, makeBackupFile, makeBackupFile, newDocument, newDocument, revertBackupFile, rootFromFile, rootFromInputStream, rootFromName, rootFromURL, setDefaultDtdLocation, setDefaultValidate, setDtdLocation, setValidate, userFileChooser, userFileChooser, writeXML, xmlDir
-
Field Details
-
nameStore
-
baseFileName
-
-
Constructor Details
-
OlcbEventNameStoreXml
-
-
Method Details
-
migrateFromIdTagStore
The original implementation of this store was via the IdTagManager class. This is now viewed as a mistake. This method takes names stored in the IdTagManager and migrates them to the dedicated local store.Note when this actually migrates, it opens and loads the IdTag Manager which can result in name confusion when Reporters are later created by a panel file. If this has already happened, the internal reporters generated by that have to be removed before this migration takes place. This means that there's no real good place to run this as part of JMRI startup. Instead, it's left as a public method so it can (when needed) be invoked by e.g. a script after the name clean up has been done.
-
store
- Throws:
IOException
-
load
-