Extender: Different property files are accessed between STV code and Java lib

[Morgan111]

In the NetFlix import I have cases where I set and get properties from the Studio code, and the Java code running in a jar file also gets and sets properties. On the Extender all of these operations are occurring in Program Files/SageTV/SageTV/clients/xxxxxxx.properties as I would expect. The get/set operations done in the Java library are interacting with Program Files/SageTV/SageTV/Sage.properties.

So when the config screens prompt for configuration data and write to the client/xxxx.properties file, the Java library code does not see it because it is looking in the server Sage.properties file. Is that the way it works or is there some problem in where files are installed or maybe the way the Java library is configured?

[GKusnick]

How are you doing the API calls in Java? If you call sage.SageTV.api, you're using the server's UI context and will access Sage.properties. If you call sage.SageTV.apiUI with the correct UI context, you'll access the specific properties file for that context.

If you're using my API wrappers, you need to instantiate the API wrapper class with a UI context in order to get the correct per-client properties file.