Bugzilla – Full Text Bug Listing
| Summary: | Creating container for InstanceSpecification fails the first time | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Klaas Gadeyne <klaas.gadeyne> | ||||
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cletavernier | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Side effect of Bug 402525: [Widgets / Transactions] Papyrus dialogs should be transactional I mark it as a duplicate, but it is really a side-effect. Anyway, fixing Bug 402525 will also fix this one. *** This bug has been marked as a duplicate of bug 402525 *** |
Created attachment 230936 [details] Empty container selection window Build id: 20130320-2352 Papyrus UML (Incubation) 0.10.0.v201305131026 org.eclipse.papyrus.sdk.feature.feature.group Eclipse Modeling Project Steps to reproduce: - Create a UML model with "Class1" containing "Class2" - Create an InstanceSpecification "InstanceSpecification1" (via Pallete -> InstanceSpecification), and set the Classifier of InstanceSpecification to Class1 (via the properties view) - Add a slot "class2slot" to InstanceSpecification1 (via Palette), and set its defining feature to "Class2" [Now we are going to try to create and InstanceValue for class2Slot, which is linked to and InstanceSpecification of Class2] a/ Select the slot "class2slot" in the diagram b/ In the properties view, click the "+" button (Add Value) for the Value field and select "InstanceValue" c/ In the "create a new InstanceValue" window, click on "+" (Create a new Object) next to the Instance field and select "InstanceSpecification" d/ A new window pops up for the Creation of the new InstanceSpecification. When trying to select the container for the new InstanceSpecification, everything is empty (see screenshot in attach). Workaround: Create the InstanceValue without filling the "Instance" field in a first step. When now performing steps c/ and d/ again, everything works fine.