Ticket #786 (closed Enhancement: fixed)
Core API: topic references should be supported for Compositions as well
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.6 |
Component: | DeepaMehta Standard Distribution | Version: | 4.5 |
Keywords: | Cc: | dgf, Malte | |
Complexity: | 3 | Area: | Application Framework / API |
Module: | deepamehta-core |
Description
Currently a Topic Reference to a child topic is only functional in conjunction with Aggregation Definition. This design reflects the fact that with Compositions in contrast the child topic can't be exist independently from the parent. That's the very definition of Composition. So, conceptually it seemed contradictory to refer to a child, which, at this moment, apparently exists already independent from the parent.
However, technically there are situations when the child exists already, also for Compositions. So the Core should support Topic References also in conjunction with Composition Definition.
Note: Topic Reference here refers to 1) the ChildTopics's setRef() method and the TopicReferenceModel class (Core API), and 2) the ref_id: and ref_uri: prefixes (REST API).