We aew

> Hum, in which way do you think it's doing "too many things"? Do you see a better way for accessing configuration values?

The fact that it is not only reading the property but it is also used to create an instance from the value. It is just a feeling.

> I like the idea of the createInstance() sub-level in the fluent API, I'll give that a try. But we also should consider that this is an internal utility API without user exposure, so I don't want to gold-plate this thing ;)

+1
I'm proposing these changes because I think they are not much different from what you have already done.