[ETCH-222] Refactoring of EtchObject TypeHandling

• Type: Task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 1.5.0
• Component/s: binding-cpp
• Assignee: Unassigned
• Reporter: Martin Veith
• Created: 07/Mar/12 10:57
• Updated: 04/Apr/14 11:58

Description

At the moment a derived class of EtchObject can set the EtchObjectType only through the constructor. This causes that every class has to provide a constructor to set the EtchObjectType information. If someone would like to derive from a certain class, this class must have a special constructor to be able to set the EtchObjectType correctly.
Therefore we need another method named setObjectType(EtchObjectType of current object, EtchObjectType of the parent, EtchObjectType of component (if it is an array), int dimension (if it is an array)) which is implemented by EtchObject. Each individual class has to call the setObjectType in its constructor to set the correct type information.
The type hierarchy can then be stored in a List in EtchObject. This makes it possible to extend EtchObject with another method "instanceOf" to check the dependency graph.

One example would be the dependency hierarchy EtchObject -> EtchTypeValidator -> EtchTypeValidator_Boolean