Eclipse Community Forums: EMF » EMF 2.3.0M5 unsettable property

Help

Home

Home » Modeling » EMF » EMF 2.3.0M5 unsettable property

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

EMF 2.3.0M5 unsettable property [message #407248]

Tue, 20 February 2007 13:07

Stephane fournier

Messages: 340
Registered: July 2009

Senior Member

Hi,

I used the "unsettable" property with EMF 2.2.x, and it works fine.
I moved to EMF 2.3.0M5 to get Java 5.0 compliance, but it seems that the
"unsettable" property is no longer taken into account at generation time.
The generated code includes set metho

Report message to a moderator

Re: EMF 2.3.0M5 unsettable property [message #407249 is a reply to message #407248]

Tue, 20 February 2007 13:15

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Stephane,

The generated code should include a set method. If you make the feature
be not changeable, then there won't be a set method. But this hasn't
changed from 2.2.x to 2.3...

Stephane wrote:
> Hi,
>
> I used the "unsettable" property with EMF 2.2.x, and it works fine.
> I moved to EMF 2.3.0M5 to get Java 5.0 compliance, but it seems that
> the "unsettable" property is no longer taken into account at
> generation time.
> The generated code includes set metho
>

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

Report message to a moderator

Re: EMF 2.3.0M5 unsettable property [message #407250 is a reply to message #407249]

Tue, 20 February 2007 13:21

Stephane fournier

Messages: 340
Registered: July 2009

Senior Member

Ed,

First, I am sorry my post was sent too early, but you guess my question.
I'll try that right now.

Stephane.

Ed Merks wrote:

> Stephane,

> The generated code should include a set method. If you make the feature
> be not changeable, then there won't be a set method. But this hasn't
> changed from 2.2.x to 2.3...

> Stephane wrote:
>> Hi,
>>
>> I used the "unsettable" property with EMF 2.2.x, and it works fine.
>> I moved to EMF 2.3.0M5 to get Java 5.0 compliance, but it seems that
>> the "unsettable" property is no longer taken into account at
>> generation time.
>> The generated code includes set metho
>>

Report message to a moderator

Previous Topic:	Attribute default value
Next Topic:	confusing explanation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 10:09:47 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter