From Client:
Also with regards to the EmaConfig.xml file (and files it references, such as RDMFieldDictionary and enumtype.def), how do other clients go about handling relative paths for these files?
The locations of configuration files like these differ for us between testing and production environments. Typically we handle this by loading files as classpath resources, but that the file names specified in EmaConfig.xml must be relative physical paths.
We can re-write the file paths at run-time before calling the Refinitiv API, but wanted to make sure there isn't a better solution first.