|
| Re: Attribute vs Containment Reference Relationship [message #1743208 is a reply to message #1743205] |
Tue, 13 September 2016 06:10  |
Eclipse User |
|
|
|
|
Of course they're both EStructuralFeatures. But the type of an EAttribute must be an EDataType and the type of an EReference must be an EClass. In terms of the structure that's produced from the model, instances of EDataTypes are leaf values in the structure; the value cannot be inspected further using EMF reflection. To be EDataType.serializeable, it must be possible to convert the value to a string representation for which it's possible to produce the original value (or one equal to it). Instances of EClasses are necessarily EObjects. EObjects form a graph of interconnected information than can be inspected using EMF reflection (EObject.eGet). EReferences that are containment references induce a tree (recursively EObject.eContents); container references (EObject.eContainer) are the reverse direction of that tree. EReferences that are cross references (not containment and not container) are cross links (EObject.eCrossReferences) between the nodes in the tree.
|
|
|
Powered by
FUDForum. Page generated in 0.02827 seconds
Home