SDL TMS 11.0 | Non-default options from the Options XML file are not respected in SDL TMS

Symptoms: 
Initial issue:

For custom file types that use an Options XML file containing non-default options (configured in SDL Trados Studio), SDL TMS was still applying the default setting for those options. 
The issue would manifest for custom file types using one of the following Pre-Processing tools:
  • Delimited Text v 2.0.0.0
  • Html File v 2.0.0.0 with predefined/custom HTML4/5 configuration
  • RegEx v 1.0.0.0
  • XML v 1.3.0.0/XML v 1.2.0.0 with default embedded content processor whether PlainText or HTML4/5
  • XML v 1.3.0.0/XML v 1.2.0.0 with custom embedded content processor

Second issue:
The Engineering team produced a fix for this issue which unfortunately introduced low performance when processing messages for files types using the above mentioned Pre-Processing tools.

Explanation: 
Initial issue: 
SDL TMS was ignoring the non-default options that users had specifically selected when creating the .SDLFTSETTINGS file in SDL Trados Studio. When making use of that file in a custom file type in SDL TMS, the options applied were actually the default ones. 

Second issue: 
When dealing with filters, resource assemblies need to be loaded. The performance issue was caused by the fact that these libraries were loaded twice, once by core components and another time by the TMS locator.

Resolution: 
This fix resolves the initial issue, so that SDL TMS now respects the non-default settings from the Options XML, even for files types using the above mentioned Pre-Processing tools. This fix also prevents the redundant loading of resources, ensuring a normal level of message processing.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS11.0 Hotfix for TMS-5287.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/Hotfix.

Note: 
This fix is a follow up on the Combined Hotfix for TMS 11.0 and the ERRATUM for Combined Hotfix for SDL TMS 11.0.

As the initial issue was detected in a previous version of SDL TMS and as per SDL Engineering policy, the Engineering team provides this hotfix only for the latest release of SDL TMS. This is to encourage our customers to run the latest version of SDL TMS to benefit from the latest features and fixes.