Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » EMF 2.3.0M5 unsettable property
EMF 2.3.0M5 unsettable property [message #407248] Tue, 20 February 2007 13:07 Go to next message
Stephane  Fournier is currently offline Stephane FournierFriend
Messages: 273
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
Re: EMF 2.3.0M5 unsettable property [message #407249 is a reply to message #407248] Tue, 20 February 2007 13:15 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 26285
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
>
Re: EMF 2.3.0M5 unsettable property [message #407250 is a reply to message #407249] Tue, 20 February 2007 13:21 Go to previous message
Stephane  Fournier is currently offline Stephane FournierFriend
Messages: 273
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
>>
Previous Topic:Attribute default value
Next Topic:confusing explanation
Goto Forum:
  


Current Time: Sat Dec 20 11:28:35 GMT 2014

Powered by FUDForum. Page generated in 0.01649 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software