Details
-
Type: New Feature
-
Status: Open
-
Priority: Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Unexpected problems on the client side can occur if the XML configuration files (Limits/Parameters/Presets) do not conform to their schema.
Some kind of configuration validation step is needed in the build or packaging phase, to flag up issues related to buggy configuration files before they get deployed to a server. I'd also imagine such a validation would be useful for JABA administrators who are tinkering with these configuration files.
Some kind of configuration validation step is needed in the build or packaging phase, to flag up issues related to buggy configuration files before they get deployed to a server. I'd also imagine such a validation would be useful for JABA administrators who are tinkering with these configuration files.