TreeHandlerManager should set properties recursively to allow flexible tree
configurations
------------------------------------------------------------------------------------------
Key: MAGNOLIA-2875
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2875
Project: Magnolia
Issue Type: Improvement
Components: admininterface
Affects Versions: 4.1.1
Reporter: Will Scheidegger
Assignee: Philipp Bärfuss
Attachments: TreeHandlerManager.recursive.patch
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
