Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359866

Summary:	Editing constraints using VSL xtext editor only succeeds after manually creating OpaqueExpression
Product:	[Modeling] Papyrus	Reporter:	Klaas Gadeyne <klaas.gadeyne>
Component:	Marte	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.8.1
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Klaas Gadeyne

2011-10-04 12:12:32 EDT

Build Identifier:  20110916-0149

Using the xtext VSL constraint editor on a constraint only works if manually replacing the 'literal string' specification by an opaque expression with language set to VSL manully before.  This is very unintuitive, and no error or warning is raised at all.

Compare this fi. with the behaviour of the xtext OCL constraint editor.  In this case, as expected, the 'literal string' specification is replaced by an OpaqueExpression, with language set to OCL and the contents are correctly transferred from the xtext editor.

(note: in both cases, the diagram editor seem to suffer from a refresh problem too)


Reproducible: Always

Steps to Reproduce:
1. Set the default editor to the xtext VSL constraint editor.  By default the specification of the constraint which is created is 'literal string' (see bug #322994)
2. Create a small model using a constraint.  Click on it to edit the expression of the constraint in the xtext pop-up editor.
3. Click anywhere on the model

=> All Editions are lost

Comment 1 Klaas Gadeyne

2011-10-05 03:40:53 EDT

Update version info: MARTE profile (Incubation) 0.8.1.v201109242121