> On May 2, 2016, at 9:32 AM, Chris Pike <[email protected]> wrote: > > Currently, calling Config will give you both local and remote config, so the > only code calling LocalConfig is code loading properties needed for setting > up the connection. I'm not sure if there is a great way to abstract it any > further. Potentially, we could create a RemoteConfig class and let Config be > the common interface to both. But it would have to keep state on whether > remote config was loaded, and then try to load it every time any of the > getProperty methods was called until successful.
Now is prolly a good time to review the capabilities of the underlying framework commons config: https://commons.apache.org/proper/commons-configuration/userguide/user_guide.html I’ve got to think that this problem has already been solved. Anyway I’m looking at the user guide now…. Shawn
