Eclipse Community Forums: EMF » Copying derived attribute

Help

Home

Home » Modeling » EMF » Copying derived attribute(Derived attribute)

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

Copying derived attribute [message #1434835]

Tue, 30 September 2014 17:19

Al B

Messages: 47
Registered: June 2012

Member

Is it possible to keep the content of derived attributes when one copies instances of a model element from one editor or another? In my case, the metadata attribute is gone in the destination because it's a derived attribute.

Copied source:

<xxegsn:ArgumentPattern identifier="P1">
    <node xsi:type="xxegsn:Goal" identifier="G1" description="Requirement (ID) {id1::int} holds">
      <data xsi:type="xxegsn:PatternBehavior" metadata="hasParam(id1, int)" toBeInstantiated="true"/>
    </node>
 </xxegsn:ArgumentPattern>

Pasted target:

<xxegsn:ArgumentPattern identifier="P1">
    <node xsi:type="xxegsn:Goal" identifier="G1" description="Requirement (ID) {id1::int} holds">
      <data xsi:type="xxegsn:PatternBehavior" toBeInstantiated="true"/>
    </node>
 </xxegsn:ArgumentPattern>

Report message to a moderator

Re: Copying derived attribute [message #1434878 is a reply to message #1434835]

Tue, 30 September 2014 18:49

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Al,

Comments below.

On 30/09/2014 7:19 PM, Al B wrote:
> Is it possible to keep the content of derived attributes when one
> copies instances of a model element from one editor or another? In my
> case, the metadata attribute is gone in the destination because it's a
> derived attribute.
The copier deliberately omits derived features because they're generally
derived from context. They're typically transient, volatile, and not
changeable as well...
>
> Copied source:
> <xxegsn:ArgumentPattern identifier="P1">
> <node xsi:type="xxegsn:Goal" identifier="G1"
> description="Requirement (ID) {id1::int} holds">
> <data xsi:type="xxegsn:PatternBehavior" metadata="hasParam(id1,
> int)" toBeInstantiated="true"/>
> </node>
> </xxegsn:ArgumentPattern>
>
> Pasted target:
> <xxegsn:ArgumentPattern identifier="P1">
> <node xsi:type="xxegsn:Goal" identifier="G1"
> description="Requirement (ID) {id1::int} holds">
> <data xsi:type="xxegsn:PatternBehavior" toBeInstantiated="true"/>
> </node>
> </xxegsn:ArgumentPattern>
Why is the feature marked derived? From what is it derived? What
wouldn't work if you didn't mark it derived? Is it changeable? What's
the effect if it's set explicitly? I.e., is that value still respected
or is it still derived? Perhaps you're using this more like a computed
default than as a feature that's truly derived, in which case it's value
is *always* determined from the values of other features...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Copying derived attribute [message #1434896 is a reply to message #1434878]

Tue, 30 September 2014 19:30

Al B

Messages: 47
Registered: June 2012

Member

Ed,

It's derived from the content in the description attribute and it cannot be set explicitly or edited because it's read-only.

description="Requirement (ID) {id1::int} holds"

However, you provided me with information I was looking for; which is the copier deliberately omits derived features because they're generally derived from context. Thus, in my case, the metadata attribute was neither transient, volatile, and not changeable so it shouldn't be set as derived. Instead, it should be just read-only.

Thanks!

[Updated on: Tue, 30 September 2014 19:46]

Report message to a moderator

Re: Copying derived attribute [message #1435132 is a reply to message #1434896]

Wed, 01 October 2014 04:02

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Al,

I assume that "it can't be set explicitly" implies its not changeable,
in which case you can't call eSet for that feature, which is how the
copier would copy it. Of course that seems contradictory to the fact
you show it in the serialization because normally the deserializer will
try to set it when its present. Also, you show the description present
in the copy, so certainly the derivation has the value it needs for its
derivation. Perhaps it's more an issue of which point in time you're
computing the derivation? If you look in
org.eclipse.emf.ecore.util.EcoreUtil.Copier.copy(EObject) you can see it
copies the features in the order in which they appear in the model, so
if a containment reference comes before an attribute, that reference's
containment tree will be copied before the attribute...

On 30/09/2014 9:30 PM, Al B wrote:
> Ed,
>
> It's derived from the content in the description attribute and it
> cannot be set explicitly or edited because it's read-only.
>
> description="Requirement (ID) {id1::int} holds"

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	[Xcore] overriding value of a superclass attribute
Next Topic:	[CDO] on Android

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 12:48:48 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter