Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366396 - Visualization of slot-Values is not compliant with the latest UML standard
Summary: Visualization of slot-Values is not compliant with the latest UML standard
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-12 08:31 EST by Marc-Florian Wendland CLA
Modified: 2012-06-28 03:13 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc-Florian Wendland CLA 2011-12-12 08:31:00 EST 
Currently in Papyrus, a slot with a value is visualized as follows:

definingFeatureName : value

This is not compliant with OMG 2.4 standard, where a slot is either visualized as

definingFeatureName = value, or
definingFeatureName : Type = value (see attachment).

I would expect papyrus to cope with both possibilities in the future, maybe using the ShowContents functionality to choose between both representations.
Comment 1 Yann Tanguy CLA 2011-12-12 09:22:25 EST 
This is normal somehow as Papyrus rely on Eclipse UML2 implementation which does not implement UML 2.4 specification (its 2.2 I think).

The UML 2.4.1 support is in progress (both in Eclipse UML2 plug-in and Papyrus) and should be available in the next (Juno) release.
Comment 2 Marc-Florian Wendland CLA 2011-12-13 11:04:11 EST 
Yann, I see...

I reopened the issue anyway, since the very same counts for UML 2.2. See section 7.3.22 InstanceSpecification of UML 2.2 specification (http://www.omg.org/spec/UML/2.2/Superstructure/PDF/)
Comment 3 Camille Letavernier CLA 2012-06-28 03:13:34 EDT 
Fixed in r8447