Composite entity pattern: Difference between revisions

Revision as of 18:40, 6 February 2016

Revision as of 18:44, 6 February 2016

Line 3:

==Structure==

there are a number of strategies to implement composite entity pattern. This pattern mainly composites of compsite entity, coarse-grained object,dependent objects.<ref name=":o_cjp"/>

[[File:Composte_entity_pattern_class_diagram.png|center|Composite entity pattern class diagram]]

[[File:Composite_entity_pattern_sequence_diagram.png|center|Composite entity pattern sequence diagram]]

===Composite entity component===

Composite entity is the coarse-grained entity bean which may be the coarse-grained object, or may contain a reference to the coarse-grained object.<ref name=":o_cjp"/>

Line 9 ⟶ 13:

===Dependent objects===

It is an object, which can contain other dependent objects (there may be a tree of objects within the composite entity), that depends on the coarse-grained object and has its life cycle managed by the coarse-grained object.<ref name=":o_cjp"/>

==Consequences==

According to Oracle description of the pattern, consequences includes eliminating inter-entity relationships, improving manageability by reducing entity beans, improving network performance, reducing database schema dependency, incresing object granularity, facicilitating composite transfer object creation and overhead of multi-level dependent object graphes.<ref name=":o_cjp"/>