| Summary: | [DeploymentDiagram] Can't model communication paths between nodes. | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Steve Blackwell <zephod77> |
| Component: | Diagram | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | alan77codebits, anatoly.shirokov, BlackBsd, rayl |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Steve Blackwell
This problem still exists in 0.8.0.v201106151827. Manifestation links also don't work. It is not possible to draw one on a deployment diagram. Still present in 0.8.2.v201202150957 Links should be allowed to indicate connections among nodes (e.g. SCSI, TCP/IP, etc...) I can reproduce this behavior 0.10.X. However, in general a "link" in Papyrus denotes a link between a comment and an element (annotated-element) and works like that for the deployment diagram. Having said that, the UML standard proposes to use associations for modeling communication paths between nodes and Papyrus does not provide this option. Therefore I changed the title of this bug. Hello, any update on this bug? Any news? this seems to work in neon.2 I can create two nodes on a deployment diagram, then use the CommunicationPath item on the Links palette to create a path between them. the Link item on the Links palette also works to create a link to a Comment (as comment 4 mentioned) |