Community
Participate
Working Groups
Build Identifier: If you drag a delegation connector from the model into a diagram, it will start and stop at the port of a property, although one of the connector ends has no part with port (i.e. should point to the proper port of the composite itself). Reproducible: Always
@Ansgar: Can you precise what is a delegation connector? I don't understand what is expected in this bug.
@Ansgar: Can you provide an example?
Created attachment 265874 [details] UML example model The description was indeed not very clear. The basic problem is that the same semantic port can be represented visually at several times in the diagram. While the choice of the "right" representation could be non-deterministic, the current implementation makes clearly wrong choices. - Open the example model. The port1 is defined in class1 and inherited by class2. It is also present on a part "class1". Thus, the same port is visually represented three times. - Remove the connector1 from diagram - Drag connector1 from model-explorer back into the diagram. The connector now connects the two parts class3 and class1. The latter should not be the case, since the part-with-port is null. - Variant: hide part class1 before dragging connector1 back into diagram. The connector connects the port1 visually attached to class1 which results in an invalid composite structure diagram - Remove connector2 - Drag connector2 back into the diagram. It is shown as a loop to the same visual representation of the port (resulting in an invalid diagram) While the example might seem far-fetched, similar cases are actually used in Papyrus SW designer where "standardized" ports are defined in a library and inherited by multiple components.
