|
Problem:
-----------
A lot of beans are configured by properties stored in a node and the code is therfore full of such statements
String value = node.getNodeData('myProperty').getString();
bean.setMyProperts(value);
...
In the dialogs/controls for example a generic setConfigValue() method is used everywhere and nobody knows which kind of properties a control realy has. In the future the controls must define there properties (using getter and setter).
Solution:
-----------
We shouldn't implement a new persistence framework for JCR (other will do that better), but we need an easy to use Util:
- BeanUtils.setProperties(bean, node)
- could handle Maps and Collections too
Hint: Some of the beans will be configured by Spring. We must think about keeping the configuration in the config repository using some custom BeanDefinition registration. A primar start could be:
http://static.springframework.org/spring/docs/1.2.x/api/org/springframework/beans/factory/support/DefaultListableBeanFactory.html
|