mcgillram / touchram / issues / #157 - Allow to pass null as value of message call — Bitbucket

Issue #157 resolved

Matthias Schoettle created an issue 2014-07-24

Currently, when calling a message and specifying the actual values for the parameters, existing structural features or literals can be specified. However, in some cases it might be necessary to pass null. Support for this should be added (probably in form of an OpaqueExpression.

Comments (4)

Matthias Schoettle reporter
- assigned issue to
  
  Matthias Schoettle
- changed milestone to MODELS 2014 Demo
- 2014-08-28T15:03:10+00:00
Matthias Schoettle reporter
One way could be to introduce a LiteralNull (as a subclass of ValueSpecification) to define a null value. This is how it is done in the UML metamodel.
- 2014-08-28T15:04:25+00:00
Matthias Schoettle reporter
References issue ~~#157~~: Added LiteralNull to metamodel and re-generated code.

→ <<cset fb4d1cc4c98f>>
- 2014-09-18T02:10:33+00:00
Matthias Schoettle reporter
- changed status to resolved
Resolved issue ~~#157~~: Added support for LiteralNull to ValueSpecificationHandler.

→ <<cset c5035c610963>>
- 2014-09-18T02:10:33+00:00
Log in to comment

Assignee: Matthias Schoettle

Type: enhancement

Priority: minor

Status: resolved

Component: GUI

Milestone: MODELS 2014 Demo

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!