| Summary: | [ActivityDiagram] Activity Diagram should be able to handle correctly Exception Handler element | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Arthur Daussy <arthur.daussy> |
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | faure.tristan, klaas.gadeyne, pauline.deville |
| Version: | 0.8.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 366159 | ||
| Bug Blocks: | |||
|
Description
Arthur Daussy
TODO : UML Documentation define several constraint : [1] The exception handler and its input object node are not the source or target of any edge. [2] An edge that has a source in an exception handler structured node must also have its target in the handler, and vice versa. [3] If the protected node is a StructuredActivityNode with output pins, then the exception handler body must also be a StructuredActivityNode with output pins that correspond in number and types to those of the protected node. [4] The handler body has one input, and that input is the same as the exception input. For now only constraint 4 as been implemented. The other will be implemented later. This bug will depend of Bug 363459 because both have quite the same representation so all commit will be under this bug. Correction : This bug will depend of Bug 366159 because both have quite the same representation so all commit will be under this bug. One other constraint: [5] The target of this edges should be a ObjectNode (UML2.5 15.7.13) |