Bug 511440 - Default rules do not handle non string many attributes correctly
Summary: Default rules do not handle non string many attributes correctly
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-02-01 04:45 EST by Melanie Bats CLA
Modified: 2017-03-10 09:15 EST (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 Melanie Bats CLA 2017-02-01 04:45:15 EST 
The default rules do not handle the non string many attributes correctly. For example if you have in your metamodel a char attributes with a upper bound equals to -1, then it will be represented by the default rules thanks to a list which is good but the char values are not represented in the table content. This results by an empty table in case of non string attribute.
The problem exists with any non strnig type : char, boolean, date, double, int, enum, float, long, short...

RCPTT tests demonstrate the problem, the tests are named "DefaultRules**AttributeMany" and are available in org.eclipse.sirius/plugins/org.eclipse.sirius.tests.rcptt/case/properties/defaultrules