YADE job should use element values that are not defined as CDATA

Current Situation

• YADE supports the XML configuration
• For the management of YADE XML configuration files SOS provides the schema-aware Editors for XML Configuration:
  • The functionality to manage YADE and System Monitor configuration files is directly available from JOC Cockpit.
    • JOC Cockpit always generates all element values as CDATA
      • eg: <DisableErrorOnNoFilesFound><![CDATA[true]]></DisableErrorOnNoFilesFound>
  • The .NET XML Editor
    • This editor generates some element values not as CDATA
      • eg: <DisableErrorOnNoFilesFound>true</DisableErrorOnNoFilesFound>
    • This values will be ignored by a YADE job and not used
  • This problem concerns all jobs that uses a settings parameter and the element values are not in a CDATA section

Desired Behavior

• YADE should use all configured element values regardless of whether a element value declared in a CDATA section or not.

Workaround 1

• set all element values as CDATA

Workaround 2
A patch is available for download with JobScheduler releases:

• JobScheduler 1.13.1, 1.13.2
  • Download the patch patch-20191212-YADE-549-1.13.1-1.13.2.zip
  • Extract the patch-20191212-YADE-549-1.13.1-1.13.2.zip to any location
  • Copy patch-20191212-YADE-549-1.13.1-1.13.2.jar to
    • {$scheduler_home}/lib/patches
  • Perform a restart