I'm in need of some design advice. Suppose I have already something that can load a properties file, and turn it into a

Provider<Map<String, String>>

. And suppose that I have a

MapProperty

whose sole purpose is to aggregate the contents of multiple properties files. Now, suppose that the values in the resulting map contain references to keys of the map (ie. something like

foo=${bar}

or the like). I'm trying to obtain a

Provider<Map<String, String>>

that would provide the "fully resolved" map, while trying to avoid having to calculate substitutions repeatedly, nested substitutions, and all your typical pitfalls. How good would using a second

MapProperty

be as an intermediate store?