[#GRT-10] Facilitate copying and moving object hierarchies from one parent to another

GReAT

Facilitate copying and moving object hierarchies from one parent to another

Created: 07/Jun/04 11:55 AM Updated: 12/Jul/04 11:53 PM

Return to search

Component/s:

Graph Rewrite Engine (GRE), Code Generator

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Description

« Hide

say there are two parents P1 and P2 and there is a child C1. Then if the user draws a pattern

P1<>----C1-----<>p2

Where, C1 are marked as "Bind", the composition from P1 to C1 is marked as "Delete" and and the compositon from P2 to C1 is marked as "CreateNew".

This pattern means that the user wants to move C1 and its contained hierarchy from parent P1 to parent P2.

Such a pattern should be identified in GRE and CG. The move should change the parent attribute only. In the specific API it is
obj.parent() = <new parent>

the user may want to specify a copy opertation. This should be specified using a new type of connection in the UMT called the "copy" connection. This dirrected will specify the source and the target of the copy.

1. In UMT there will be a new directed connection called "copy" that will specify the source and the destination of the copy operation.

2. Then the user can specify a new object and specify that it is a copy of another objct by using the "copy" connetion.

The figure shows a parent P1 with child C1 and a parent P2 with a child C2 where both C1 and the composition are create new. The semantics are that C2 will be created as a child of p2 and will copy all the attributes and contained children of C1.

P1 p2
<> <>
| |
| |
C1---C--->C2

In the GRE and CG the copy operation will then use the CopyObjectHierarchy funciton to implement this.

All

Comments

Work Log

Change History

Sort Order:

Change by Aditya Agrawal - 12/Jul/04 03:17 PM
Field	Original Value	New Value
Description	say there are two parents P1 and P2 and there is a child C1. Then if the user draws a pattern P1<>-----C1-----<>p2 Where, C1 are marked as "Bind", the composition from P1 to C1 is marked as "Delete" and and the compositon from P2 to C1 is marked as "CreateNew". This pattern means that the user wants to move C1 and its contained hierarchy from parent P1 to parent P2. Such a pattern should be identified in GRE and CG. To handle this semantics the CopyObjectHierarchy in UdmUtils can be used.	say there are two parents P1 and P2 and there is a child C1. Then if the user draws a pattern P1<>-----C1-----<>p2 Where, C1 are marked as "Bind", the composition from P1 to C1 is marked as "Delete" and and the compositon from P2 to C1 is marked as "CreateNew". This pattern means that the user wants to move C1 and its contained hierarchy from parent P1 to parent P2. Such a pattern should be identified in GRE and CG. To handle this semantics the CopyObjectHierarchy in UdmUtils can be used. If the move is from one parent to another within the same datanetwork. Then the move should change the parent attribute only. In the specific API it is obj.parent() = new parent If the move is from a parent in one datanetwork to a parent in another datantework then the move use CopyObjectHierarchy function to copy the objects to the other data network. Next, delete all associations the child participates in. Finally, delete the child.

Change by Gabor Karsai - 12/Jul/04 04:16 PM
Assignee	Gabor Karsai [ gabor ]	Aditya Agrawal [ aditya ]

Change by Aditya Agrawal - 12/Jul/04 11:42 PM
Comment	[ 10314 ]

Change by Aditya Agrawal - 12/Jul/04 11:53 PM
Summary	Facilitate moving object hierarchies from one parent to another	Facilitate copying and moving object hierarchies from one parent to another
Description	say there are two parents P1 and P2 and there is a child C1. Then if the user draws a pattern P1<>-----C1-----<>p2 Where, C1 are marked as "Bind", the composition from P1 to C1 is marked as "Delete" and and the compositon from P2 to C1 is marked as "CreateNew". This pattern means that the user wants to move C1 and its contained hierarchy from parent P1 to parent P2. Such a pattern should be identified in GRE and CG. To handle this semantics the CopyObjectHierarchy in UdmUtils can be used. If the move is from one parent to another within the same datanetwork. Then the move should change the parent attribute only. In the specific API it is obj.parent() = new parent If the move is from a parent in one datanetwork to a parent in another datantework then the move use CopyObjectHierarchy function to copy the objects to the other data network. Next, delete all associations the child participates in. Finally, delete the child.	say there are two parents P1 and P2 and there is a child C1. Then if the user draws a pattern P1<>----C1-----<>p2 Where, C1 are marked as "Bind", the composition from P1 to C1 is marked as "Delete" and and the compositon from P2 to C1 is marked as "CreateNew". This pattern means that the user wants to move C1 and its contained hierarchy from parent P1 to parent P2. Such a pattern should be identified in GRE and CG. The move should change the parent attribute only. In the specific API it is obj.parent() = <new parent> the user may want to specify a copy opertation. This should be specified using a new type of connection in the UMT called the "copy" connection. This dirrected will specify the source and the target of the copy. 1. In UMT there will be a new directed connection called "copy" that will specify the source and the destination of the copy operation. 2. Then the user can specify a new object and specify that it is a copy of another objct by using the "copy" connetion. The figure shows a parent P1 with child C1 and a parent P2 with a child C2 where both C1 and the composition are create new. The semantics are that C2 will be created as a child of p2 and will copy all the attributes and contained children of C1. P1 p2 <> <> \| \| \| \| C1---C--->C2 In the GRE and CG the copy operation will then use the CopyObjectHierarchy funciton to implement this.