Bug 264352 - Support multi-valued property property assignments without collection type casting
Summary: Support multi-valued property property assignments without collection type ca...
Status: RESOLVED FIXED
Alias: None
Product: QVTo
Classification: Modeling
Component: Engine (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Sergey Boyko CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation, noteworthy
Depends on:
Blocks:
 
Reported: 2009-02-10 10:05 EST by Radomil Dvorak CLA
Modified: 2009-02-20 08:40 EST (History)
0 users

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 Radomil Dvorak CLA 2009-02-10 10:05:32 EST 
Current implementation requires strict type equivalence for multi-valued property assignment.
IOW, if the left side property of an assignment is {ordered=true, unique=true}, only OrderedSet collection can be assigned.
Consequently, all other collection types have to be casted using ::asOrderedSet() operation.

Actually, we never do a direct assignment of the right side collection value as the target property (EReference)
gets only elements added, eventually including reset of the original contents.

Actually, it is quite annoying requirement and without this, the execution would perform better as we do not
necessarily need to create redundant copies of the exact collection types.
Comment 1 Radomil Dvorak CLA 2009-02-18 06:03:19 EST 
Already solved by contribution to MDT OCL.
See bug #242880 


*** This bug has been marked as a duplicate of bug 242880 ***
Comment 2 Radomil Dvorak CLA 2009-02-18 06:16:03 EST 
Woops, mistakenly closed as duplicate.
Comment 3 Sergey Boyko CLA 2009-02-18 17:52:37 EST 
Fixed.
Sample 'Uml2Rdb' accordingly updated.