[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.modeling.mdt.uml2] Re: Stereotype and Properties

Thibault,

Off the top of my head, I suspect the reason is that UML2 maps profile elements to Ecore during the profile "definition" process and data types are automatically mapped to Ecore classes (which don't have "simple" cell editor support) rather than data types.

Kenn

Thibault Landré wrote:
Hi,

I would like to understand why in the uml2 editor, it is possible to edit a property of a sterotype typed by a primitiveType whereas it is not possible when the property is typed by a Datatype ?

TestCase1 :
StereotypeA has a property (prop) typed by a primitiveType (Real for instance). StereotypeA has an extension on Metaclass 'Element'
When applying the stereotype to a class, the properties view allows you to edit the property 'prop'.


TestCase2 :
StereotypeB has a property (propB) typed by a datatype (Time for instance). StereotypeB has an extension on Metaclass 'Element'
When applying the stereotype to a class, you can't edit the property of StereotypeB (propB is not displayed in the properties view).


Why ?
I have look into the UML OMG specification to see if a difference between a PrimitiveType and DataType could explain this behaviour, but I have not found any clue.


Thanks,

Thibault