Eclipse Community Forums: EMF » Read-Only attributes persisted in model.uml and caused into error

Home » Modeling » EMF » Read-Only attributes persisted in model.uml and caused into error (Error is shown when loading a diagram with an element and its readonly attribute)

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

Read-Only attributes persisted in model.uml and caused into error [message #1162612]

Wed, 30 October 2013 13:56

Erik Schondorff

Messages: 25
Registered: October 2013

Junior Member

Hello community,

I have a read-only attribute defined in my *.ecore model, so it has no setAttribute - method in the corresponding *.impl.java.
This causes in an error when loading a diagram, which has a model element with its read-only attribute because the attribute is persisted in the model.uml and the setAttribut-method does not exists. What can I do, when a read-only attribute should not be persisted in the Papyrus - model.uml?

Thanks in advance.

Erik

Report message to a moderator

Re: Read-Only attributes persisted in model.uml and caused into error [message #1162649 is a reply to message #1162612]

Wed, 30 October 2013 14:22

Ed Merks

Messages: 33212
Registered: July 2009

Senior Member

Erik,

An attribute for which isChangeable is false should almost always have
isTransient true. Then it won't be serialized and then the deserializer
won't see something in the serialization it wants to set into the
model. It's also typically the case that an attribute for which
isChangeable is false, also has isDerived true because how else could an
instance ever have a value different from the default unless it's
derived from something else that can actually be changed?

On 30/10/2013 2:56 PM, Erik Schondorff wrote:
> Hello community,
>
> I have a read-only attribute defined in my *.ecore model, so it has no
> setAttribute - method in the corresponding *.impl.java.
> This causes in an error when loading a diagram, which has a model
> element with its read-only attribute because the attribute is
> persisted in the model.uml and the setAttribut-method does not exists.
> What can I do, when a read-only attribute should not be persisted in
> the Papyrus - model.uml?
>
> Thanks in advance.
>
> Erik

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

Report message to a moderator