Project

General

Profile

Actions

bug #4919

open

improve AdvancedBeanInitializer

Added by Andreas Kohlbecker almost 9 years ago. Updated about 2 years ago.

Status:
New
Priority:
New
Category:
cdmlib
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:
Tags:

Description

The AdvancedBeanInitializer needs improvements:

  1. autoinitialization of Collection items in case of bean.collection where an Autoinitializer exists for the type of the collection items - DONE : 72b0ad09b r23851

  2. autoinitialization of asscoiated beans as in case of bean.subBean where an Autoinitializer exists for the type of the subBean items

  3. calls to PropertyUtils.getProperty() are causing unwanted initalization in some cases, e.g. in @initializeNodeNoWildcard()@:

 Object propertyValue = PropertyUtils.getProperty(parentBean, propertyName);
 preparePropertyValueForBulkLoadOrStore(node, parentBean, property, propertyValue);
  1. each bean passed to the initializeAll() method of the AdvancedBeanInitializer is auto-initialized independently from the initStrategy (see snipped below), this should improved by making use of the hql returned by addAutoinitFetchLoading()
//autoinitialize
for (Object bean : beanList){
   autoinitializeBean(bean);
}

Related issues

Related to EDIT - task #7054: clean up initialization strategy using '.representations'In ProgressAndreas Müller

Actions
Actions

Also available in: Atom PDF