[news.eclipse.modeling.m2m] Re: EMF Changeable problem

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Max,

If you make something unchangeable you should expect never to be able to 
change it.  So generally it will be transient and likely will be 
derived, i.e., its value is computed from the value of something else.  
Perhaps you just want to suppress the setters from the API to make it 
difficult but not impossible for the user to change the value.


Max Bureck wrote:
> Hello,
>
> one more problem:
> I tried to create an EMF-Model with ATL, that applies to an Ecore 
> metamodel of mine. On one attribute of the metamodel I set the 
> property changeable to false. My intention was to forbid the user of 
> the output-model to change some of the created/generated values.
> Unfortunately ATL complains, that it cannot set this attribute 
> ("message: feature name is not changeable"). But there must be a way 
> to initialize the attribute. What sense does a read-only attribute 
> make, when there is no way to set the standard-value? Or can this only 
> be used in combination with a static default value in the metamodel 
> and the modification has to be controlled over the editor for the 
> generated model-files?
>
> Kind regards,
> Max