After examining this test more closely, I realized that this was the
intended
behaviour. The configuration inheritance mechanism was design to inherit
entire
configurations from parents, not individual attributes. The usefulness in
this is
that you can specify a high level configuration for key X, then your
application can
just start using child key Y (without supplying configuration), and the
configuration
would be automatically created as inherited from X.
It might be possible to allow per-attribute inheritance, however, I think
this would
add too much memory overhead for the "benefit" it provides, because each
field would
need to be remembered as inherited or not. Currently only entire configs
remember if
they were inherited.
Clearly, you've found a really good candidate for needing some detailed
documentation.
Comment #3 on issue 32 by troy.kin...@gmail.com: DefaultStatsConfigBuilder
does not respect root configuration
http://code.google.com/p/stajistics/issues/detail?id=32
Closing. Only documentation is needed (which is a general problem).