Currently LocalConfiguration is responsible to:
1) provide access to configuration properties and
2) provide some methods that are largely used in the framework and
3) keeping states of processing...
that is to much!
Also LocalConfiguration is accessed in a static way which leads to trouble in multithreded environments.
The new Configuration (which is already available) is pure again only providing access to configuration properties - a good step!
Now a place is needed to put the other responsibilities of curent LocalConfiguration.
My approach is to use XMLContext for this stuff.
And in addition I try to remove as much static access as possible - for the sake of thread-safe-ness and such.