Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
None
-
None
-
None
Description
ClientConfiguration optionally gets its values from multiple sources... either from a set of defaults, a set of well-known locations, or from a file specified explicitly.
It could do this in an priority hierarchy using commons-configuration's CompositeConfiguration.
One of these layers could also be the system properties, so they can be used to interpolate user configuration. I'm not sure how much value this would add to ClientConfiguration today, but it could be useful in the future for things like specifying a default namespace to connect to that corresponds to ${user.name}