Bug 507308 - feature:eAllContents set by default in the semantic candidate expression for a subNodeMapping
Summary: feature:eAllContents set by default in the semantic candidate expression for ...
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 4.1.0   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-11-09 11:23 EST by Julien Dupont CLA
Modified: 2016-11-17 05:21 EST (History)
2 users (show)

See Also:


Attachments
Example to reproduce problem (744 bytes, application/octet-stream)
2016-11-09 11:25 EST, Julien Dupont CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Dupont CLA 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 CLA 2016-11-09 11:25:13 EST
Created attachment 265279 [details]
Example to reproduce problem
Comment 2 Cedric Brun CLA 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 CLA 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 CLA 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.