The base package for the generated codebase.
The collected source definitions up to 'now'.
The canonical TO map.
The generated source files so far.
The TO map is needed to find all fields that we have to put in a class extending from one or more parents.
The map containing the transfer objects that require an interface definition so far, keyed on the canonical name of the original transfer object. This map is expected to grow while source definitions for transfer objects are generated.
The direct child parents relations are needed to navigate through the class hierarchy of the transfer objects. The toChildParentsMap is build up when the TOs are added to the toMap.
The direct parent children relations are needed to navigate through the class hierarchy of the transfer objects. The toParentChildrenMap is build up when the TOs are added to the toMap.
Adds a TO definition and update the child-parents map and the parent-children map.
Adds a TO definition and update the child-parents map and the parent-children map.
The canonical name of the TO.
The definition of the TO.
The generation aggregate.
A breadth-first list of all parent canonical names.
The base package for the generated codebase.
The canonical TO map.
A class is a parent in a multiple inheritance relation if it has a child (direct or indirect) that has more than one parent.
Find all leaf children of the given canonical name (itself not included if it is a leaf child).
Find all non-leaf children of the given canonical name (itself not included if it is a non-leaf child).
The collected source definitions up to 'now'.
The generated source files so far.
The direct child parents relations are needed to navigate through the class hierarchy of the transfer objects.
The direct child parents relations are needed to navigate through the class hierarchy of the transfer objects. The toChildParentsMap is build up when the TOs are added to the toMap.
The map containing the transfer objects that require an interface definition so far, keyed on the canonical name of the original transfer object.
The map containing the transfer objects that require an interface definition so far, keyed on the canonical name of the original transfer object. This map is expected to grow while source definitions for transfer objects are generated.
The TO map is needed to find all fields that we have to put in a class extending from one or more parents.
The direct parent children relations are needed to navigate through the class hierarchy of the transfer objects.
The direct parent children relations are needed to navigate through the class hierarchy of the transfer objects. The toParentChildrenMap is build up when the TOs are added to the toMap.
Created by peter on 18/01/17.
The generation aggregate contains information that may be needed for source definition generation and information about data and knownledge that was already collected so far in the generation process. The generation process is a recursive operation on the GenerationAggr, which can be expanded during code generation. In other words, new source definitions may be added during code generation, especially the interface definitions are expected to be added then.
The base package for the generated codebase.
The collected source definitions up to 'now'.
The canonical TO map.
The generated source files so far.
The TO map is needed to find all fields that we have to put in a class extending from one or more parents.
The map containing the transfer objects that require an interface definition so far, keyed on the canonical name of the original transfer object. This map is expected to grow while source definitions for transfer objects are generated.
The direct child parents relations are needed to navigate through the class hierarchy of the transfer objects. The toChildParentsMap is build up when the TOs are added to the toMap.
The direct parent children relations are needed to navigate through the class hierarchy of the transfer objects. The toParentChildrenMap is build up when the TOs are added to the toMap.