Gary Gregory wrote:
- For [config]: Provide an Interpolation feature that it can build on.
The [config] project, please correct me if I am off, must have a way to
plug-in how to look stuff up, hence the nice and simple VariableResolver
interface, which could be surfaced as:
String s = XXX.resolveAll(source, ..., aVariableResolver);
There is also a [config] need for multiple VariableResolvers it seems,
which means that the API can take a Map of VariableResolver or that the
client simply calls the API until all resolve calls worked. But how do
you determine that an API call resolved everything? If one cannot
(Oliver?), then we have to provide a resolveInAll(String, Map) (or other
name)?
And what about some kind of chained VariableResolver ? A resolver that
will check several resolvers or use a specific resolver depending on the
key ? Thus there is no need to have several resolveAll methods and the
actual strategy is delegated to the resolver.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
