Bug 515888 - ecore.EObject (or ecore::EObject) seems not supported in the properties views definition
Summary: ecore.EObject (or ecore::EObject) seems not supported in the properties views...
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Properties (show other bugs)
Version: 4.1.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-04-27 05:17 EDT by Cedric Brun CLA
Modified: 2017-05-05 10:12 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Brun CLA 2017-04-27 05:17:14 EDT 
In the diagram, table, tree or other dialects a domain class can be set as ecore.EObject to mean "anything". the properties view definition has a slightly different take as the domainClass might be unset, and I guess this also means "anything" in that case. 

In the properties views definition if one use ecore.EObject the result is different from "anything", in my case nothing is matched.

It is a bit troubling when you are used to leveraging "ecore.EObject"/"ecore::EObject" in the other parts of the VSM and it also prevent me from work-arounding the Bug 515884.