Bug 507308

Summary:

feature:eAllContents set by default in the semantic candidate expression for a subNodeMapping

Product:

[Modeling] Sirius

Reporter:

Julien Dupont <julien.dupont>

Component:

Diagram

Assignee:

Project Inbox <sirius.diagram-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

CC:

cedric.brun, florian.barbin

Version:

4.1.0

Keywords:

triaged

Target Milestone:

---

Hardware:

OS:

Windows NT

Whiteboard:

Attachments:

Description	Flags
Example to reproduce problem	none

Description Julien Dupont

2016-11-09 11:23:49 EST

By default when user created a SubNode mapping in the VSM, the default value of the Semantic Candidate Expression is feature:eAllContents

It's the opposite of what said to client.

It should be remove the default value.

Comment 1 Julien Dupont

2016-11-09 11:25:13 EST

Created attachment 265279 [details]
Example to reproduce problem

Comment 2 Cedric Brun

2016-11-09 13:13:33 EST

I don't know what you mean by "it is the opposite of what said to client" but there is a reason why it's done this way: an empty semantic candidate expression here can easily lead to an infinite loop, hence the choice of initializing it with a more sensible default. Removing the default value would have pretty bad consequences.

Comment 3 Julien Dupont

2016-11-15 03:15:01 EST

The feature eAllContents is not recommended. It's maybe a good things to replace it by for example feature:eContents or other thing.

Comment 4 Florian Barbin

2016-11-17 05:21:49 EST

Issue marked as "Triaged". eAllContents expression as default value is questionable since it can lead to very bad performance. By the past we already added migration participants to avoid behavior changes for existing VSM in case of default value modification.