The way trees are configured at this time is not very flexible: It's all hardcoded in configuration classes. And all you can to is select the configuration class, choose the starting path of the tree and switch between tree and browse mode.

Instead of simply selecting a configuration class by setting the configurationClass value it would be much better to have a ConfigurableTreeConfiguration class which reads its configuration at runtime from the config tree. So instead of providing a configurationClass nodeData one would provide a configuration contentNode which contains all the trees configuration info.

When I tried to do this, I noticed however that this contentNode was never turned into a bean. This is because the TreeHandlerManager does not set the properties recursively. The attached patch fixes this problem.

In a later step, I will provide a first version of the ConfigurableTreeConfiguration too.