Many of the utkscan configuration files that are shipped with the software have not been updated to the latest XML scheme. The contain legacy nodes, and other formatting issues that will cause errors when they are used with the software. We should add some error handling to the parsing routines that checks for these legacy nodes and warns the user that they exist. Legacy nodes like the Timing node need to throw an exception when they're encountered because they will really throw a monkey wrench into the parsing of the Trace and Fitting nodes.
Work to be done
Identify all of the legacy nodes that are in the configuration files
Identify the nodes that could cause critical errors.
Create a validation class (method?) that will validate nodes and look for the legacy nodes.
Update the example.xml so that it no longer contains legacy information.
Acceptance Criteria
All software compiles
Old XML files are parsed properly, and all legacy nodes are listed to the user
Old XML files throw errors if the legacy node encountered could cause a critical error.
Description
Many of the utkscan configuration files that are shipped with the software have not been updated to the latest XML scheme. The contain legacy nodes, and other formatting issues that will cause errors when they are used with the software. We should add some error handling to the parsing routines that checks for these legacy nodes and warns the user that they exist. Legacy nodes like the
Timing
node need to throw an exception when they're encountered because they will really throw a monkey wrench into the parsing of the Trace and Fitting nodes.Work to be done
Acceptance Criteria