Eclipse Community Forums: EMF » [xcore] References lower bound value not serialized

Home » Modeling » EMF » [xcore] References lower bound value not serialized(The lower bound value is not serialized in the xcore meta-model.)

Show: Today's Messages :: Show Polls :: Message Navigator

[xcore] References lower bound value not serialized [message #897602]

Tue, 24 July 2012 16:44

Regent LArcheveque

Messages: 94
Registered: May 2010

Member

Hi,

I use the properties sheet page with the XCore editor to change the lower bound value of a Reference (not array) from 0 to 1. The properties sheet page works as expected but I realize that change is not reflected in .xcore file. So if I reload the model, the lower bound value is set back to 0.

Is this an error. I used that capability with .ecore to set basic constraints.

Thanks Wink

Report message to a moderator

Re: [xcore] References lower bound value not serialized [message #897606 is a reply to message #897602]

Tue, 24 July 2012 17:06

Ed Merks

Messages: 30687
Registered: July 2009

Senior Member

<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Régent, 
 
Comments below. 
<div class="moz-cite-prefix">On 24/07/2012 6:44 PM, Régent L
Archevêque wrote: 
</div>
<blockquote cite="mid:jumjdr$iga$1@xxxxxxxxe.org" type="cite">Hi,
 
 
I use the properties sheet page with the XCore editor to change
the lower bound value of a Reference (not array) from 0 to 1. The
properties sheet page works as expected but I realize that change
is not reflected in .xcore file. So if I reload the model, the
lower bound value is set back to 0.
 
</blockquote>
Hmmm. Those Ecore properties should be read only. You're expected
to edit the Xcore directly. Only the GenModel properties should be
changeable and they are converted to @GenModel annotations. Please
open a bugzilla to make them read only. 
<blockquote cite="mid:jumjdr$iga$1@xxxxxxxxe.org" type="cite">
 
Is this an error. I used that capability with .ecore to set basic
constraints.
 
</blockquote>
You should use bounds within [], e.g., 
<blockquote> contains Writer[] authors 
</blockquote>
Things like [0..*], [1], or [1..*] all work. Just a bare [] is the
same as [0..*] 
 
There should be no need to edit Ecore properties for any purpose... 
<blockquote cite="mid:jumjdr$iga$1@xxxxxxxxe.org" type="cite">
 
Thanks ;)
 
</blockquote>
 
</body>
</html>

Report message to a moderator

Re: [xcore] References lower bound value not serialized [message #897608 is a reply to message #897606]

Tue, 24 July 2012 17:31

Regent LArcheveque

Messages: 94
Registered: May 2010

Member

Thanks Ed for the quick response.

I was not aware [1] was ok. Thanks for the tip. I'll open a bug.

Wink

Report message to a moderator

Re: [xcore] References lower bound value not serialized [message #897609 is a reply to message #897608]

Tue, 24 July 2012 17:41

Regent LArcheveque

Messages: 94
Registered: May 2010

Member

Just a little comment.

Would it be great to be able to edit ecore properties via the properties sheet page. We should be able to change containment attribute in the properties sheet page and then the keyword contains reflected in the xcore. I do not understand the rationale why it is only applicable to GenModel. Should I raise a more generic bug (nice to have).

Thanks

Report message to a moderator

Re: [xcore] References lower bound value not serialized [message #897644 is a reply to message #897609]

Tue, 24 July 2012 21:22

Ed Merks

Messages: 30687
Registered: July 2009

Senior Member

Régent,

Comments below.

On 24/07/2012 7:41 PM, Régent L Archevêque wrote:
> Just a little comment.
>
> Would it be great to be able to edit ecore properties via the
> properties sheet page.
No, I don't want to support that. Every type of change needs to be
mapped back to detailed source edits. That's a lot of work with a
hundred special cases.
> We should be able to change containment attribute in the properties
> sheet page and then the keyword contains reflected in the xcore.
There's a keyword for that; one that supports auto completion.
> I do not understand the rationale why it is only applicable to
> GenModel.
Does Java's editor support any editing via properties? Why not? For
GenModel there is no specialized syntax, only annotations, and the
mapping simple, i.e., the mapping to annotation properties can be done
reflectively.
> Should I raise a more generic bug (nice to have).
If you want to edit Ecore, you can already do that. And you can export
to Xcore after you're done. It's sufficient.
>
> Thanks
>
>

Report message to a moderator