Eclipse Community Forums: Papyrus » Existing InstanceSpecification as value

Help

Home

Home » Modeling » Papyrus » Existing InstanceSpecification as value

Show: Today's Messages :: Show Polls :: Message Navigator

Existing InstanceSpecification as value [message #1832219]

Sat, 12 September 2020 18:18

Carsten Pitz

Messages: 273
Registered: May 2015
Location: Germany

Senior Member

Hi all,

is there a way to assign an existing InstanceSpecification to a value of a Slot of an InstanceSpecification typed by a class?

I managed to assign a newly created InstanceSpecification, but not an already existing.

If I look for an existing InstanceSpecification none is displayed.

/Carsten

Report message to a moderator

Re: Existing InstanceSpecification as value [message #1832222 is a reply to message #1832219]

Sat, 12 September 2020 19:21

Ed Willink

Messages: 6985
Registered: July 2009

Senior Member

Hi

Yes. You have to assign an InstanceValue that may reference your InstanceSpecification. Bloated and confusing isn't it?

Regards

Ed Willink

Report message to a moderator

Re: Existing InstanceSpecification as value [message #1832224 is a reply to message #1832222]

Sat, 12 September 2020 19:38

Ed Willink

Messages: 6985
Registered: July 2009

Senior Member

Hi

Well perhaps not really confusing once you realize that UML is an assembler language for which IDEs provide very little high level abstraction.

For relationships IDEs generally aggregate the creation of an Association and two Properties which is helpful, but you still have to tunnel down and configure them individually. Other concepts are much more naked.

If you are mad enough to use the UML Expression classes it's hard work.

If you use OCL, you get a high level abstraction so that you do not see that

a + b

is actually at least:

createOperationCallExp("+", createVariableExp("a"), createVariableExp("b"))

This hides the VariableExp in just the same way that you would like to have known nothing about the InstanceValue that converts an InstanceSpecification to a ValueSpecification. Yes, two different semantics for the "Specification" suffix.

Regards

Ed Willink

Report message to a moderator