Bug 548130 - [Designer, transformations] Operation loop depends on operation/method order
Summary: [Designer, transformations] Operation loop depends on operation/method order
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Designer (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-11 03:42 EDT by Ansgar Radermacher CLA
Modified: 2019-06-11 03:42 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ansgar Radermacher CLA 2019-06-11 03:42:02 EDT 
The definition of a package template might contain classes having a template method applying the "LoopOperations" transformation. During template instantiation, the current implementation expands the method in a post-copy listener on the operation, but uses information from the associated method.

When the post-copy listener is called, the operation is fully copied, but - depending on the order of operations/methods in the class - the eventually not the associated method. While is would be possible to change the implementation of the transformation, this would be tricky and error prone, if the code evolves. Therefore, it's preferable to execute the additional transformations after the copy has been done.

Another issue is that signature are not correctly copied.