Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363282 - [SysML Internal Block Diagram] Inconsistent ports and connectors on IBD after changing the type of a part by retargetting the corresponding composition end on BDD.
Summary: [SysML Internal Block Diagram] Inconsistent ports and connectors on IBD after...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Yann Tanguy CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 05:56 EST by Alain Le Guennec CLA
Modified: 2011-11-23 06:22 EST (History)
2 users (show)

See Also:


Attachments
The model used to reproduced the issue. (5.51 KB, application/x-zip)
2011-11-09 05:56 EST, Alain Le Guennec CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Le Guennec CLA 2011-11-09 05:56:11 EST
Created attachment 206663 [details]
The model used to reproduced the issue.

There are inconsistent ports and connectors on IBD after changing the type of a part by retargetting the corresponding composition end on BDD.
-Take the attached model.
-Open both BDD and IBD
-Retarget the end of the composition to Block2 instead of Block1 on BDD
=> The type of part1 correctly switches to Block2, but there are two problems on IBD:
1) Block2 does not have the same port as block1, so the ports (of Block1) that used to be displayed on the frame of part1 should now be removed from the diagram (they don't belong to part1's new type Block2). The ports of Block1 themselves should of course be kept in the model.
2) The connectors should have been deleted from the model. Indeed, both have an end role that points to a port of the former part's type, which is no more relevant for the new part's type, so the connectors are now inconsistent and cannot be kept.
Comment 1 Yann Tanguy CLA 2011-11-21 04:03:10 EST
Fixed in r6252 (0.8.X).
Comment 2 Yann Tanguy CLA 2011-11-21 08:28:53 EST
(In reply to comment #1)
> Fixed in r6252 (0.8.X).
In r6262 merge into trunk.
Comment 3 Yann Tanguy CLA 2011-11-22 07:57:54 EST
> In r6262 merge into trunk.

In r6274 minor re-factoring issue (oep.service.edit is now oep.infra.services.edit).
Comment 4 Yann Tanguy CLA 2011-11-22 07:58:51 EST
(In reply to comment #3)
> > In r6262 merge into trunk.
> 
In r6274 minor re-factoring issue (oep.service.edit is now
oep.infra.services.edit). -> relates to the trunk only.
Comment 5 Yann Tanguy CLA 2011-11-23 06:22:52 EST
In r6276 (0.8.X) and r6277 (trunk):
- Distinct action when the property move is related to SysML AssociationEnd#isNavigable and don't require Association re-factor
- Destroy Association when one MemberEnd remains
- Remove MemberEnd when its type is set to null
- Set opposite AssociationEnd aggregation to None when the AssociationEnd is set to Composite while the opposite also is.