Eclipse Community Forums: EMF » How to set NAME

Home » Modeling » EMF » How to set NAME_EDEFAULT

How to set NAME_EDEFAULT [message #792648]

Tue, 07 February 2012 03:22

Eclipse User

Hi

Is it possible to set NAME_EDEFAULT for an EClass somewhere in the model
generator or in the model itself, maybe using the Ecore diagram editor?

Currently we are doing this to set the default name for each impl class
generated:

public class LongImpl extends SimpleTypeImpl implements
org.best_of_robotics.bride.datatypes.Long {
/**
* @generated NOT
*/
protected LongImpl() {
super();
name = "long";
}
....

since SimpleTypeImpl has:

public abstract class DataTypeImpl extends EObjectImpl implements DataType {

protected static final String NAME_EDEFAULT = null;
protected String name = NAME_EDEFAULT;
....

Thanks

-H

Re: How to set NAME_EDEFAULT [message #792673 is a reply to message #792648]

Tue, 07 February 2012 04:09

Eclipse User

Hugo,

Comments below.

On 07/02/2012 9:22 AM, Hugo Garcia wrote:
> Hi
>
> Is it possible to set NAME_EDEFAULT for an EClass somewhere in the
> model generator or in the model itself, maybe using the Ecore diagram
> editor?
You'll need to use the properties view to set the default value literal
property of the attribute.
>
> Currently we are doing this to set the default name for each impl
> class generated:
>
> public class LongImpl extends SimpleTypeImpl implements
> org.best_of_robotics.bride.datatypes.Long {
> /**
> * @generated NOT
> */
> protected LongImpl() {
> super();
> name = "long";
Is the name feature defined in LongImpl or in a base class?
> }
> ...
>
> since SimpleTypeImpl has:
>
> public abstract class DataTypeImpl extends EObjectImpl implements
> DataType {
>
> protected static final String NAME_EDEFAULT = null;
If you had to force it (which you don't) why wouldn't you change the
value of this declaration? After all, you'll notice that this value is
used to determine the result of eIsSet...
> protected String name = NAME_EDEFAULT;
> ...
>
> Thanks
>
> -H

Re: How to set NAME_EDEFAULT [message #793060 is a reply to message #792673]

Tue, 07 February 2012 13:17

Eclipse User

On 02/07/2012 10:09 AM, Ed Merks wrote:
> Hugo,
>
> Comments below.
>
> On 07/02/2012 9:22 AM, Hugo Garcia wrote:
>> Hi
>>
>> Is it possible to set NAME_EDEFAULT for an EClass somewhere in the
>> model generator or in the model itself, maybe using the Ecore diagram
>> editor?
> You'll need to use the properties view to set the default value literal
> property of the attribute.
>>
>> Currently we are doing this to set the default name for each impl
>> class generated:
>>
>> public class LongImpl extends SimpleTypeImpl implements
>> org.best_of_robotics.bride.datatypes.Long {
>> /**
>> * @generated NOT
>> */
>> protected LongImpl() {
>> super();
>> name = "long";
> Is the name feature defined in LongImpl or in a base class?
>> }

A base class. Guess we have to do a push down refactoring and add the
name attribute to each subclass and then set a default value for it?

>> ...
>>
>> since SimpleTypeImpl has:
>>
>> public abstract class DataTypeImpl extends EObjectImpl implements
>> DataType {
>>
>> protected static final String NAME_EDEFAULT = null;
> If you had to force it (which you don't) why wouldn't you change the
> value of this declaration? After all, you'll notice that this value is
> used to determine the result of eIsSet...
>> protected String name = NAME_EDEFAULT;
>> ...

or set this in each subclass in the code and use @generated NOT?

What would be best practice?

-H

Re: How to set NAME_EDEFAULT [message #797314 is a reply to message #793060]

Mon, 13 February 2012 05:10

Eclipse User

On 02/07/2012 07:17 PM, Hugo Garcia wrote:
> On 02/07/2012 10:09 AM, Ed Merks wrote:
>> Hugo,
>>
>> Comments below.
>>
>> On 07/02/2012 9:22 AM, Hugo Garcia wrote:
>>> Hi
>>>
>>> Is it possible to set NAME_EDEFAULT for an EClass somewhere in the
>>> model generator or in the model itself, maybe using the Ecore diagram
>>> editor?
>> You'll need to use the properties view to set the default value literal
>> property of the attribute.
>>>
>>> Currently we are doing this to set the default name for each impl
>>> class generated:
>>>
>>> public class LongImpl extends SimpleTypeImpl implements
>>> org.best_of_robotics.bride.datatypes.Long {
>>> /**
>>> * @generated NOT
>>> */
>>> protected LongImpl() {
>>> super();
>>> name = "long";
>> Is the name feature defined in LongImpl or in a base class?
>>> }
>
> A base class. Guess we have to do a push down refactoring and add the
> name attribute to each subclass and then set a default value for it?
>

Ok, so the solution is to use Interfaces as super types and thus the
generator will produce an implementation code for each field declared in
the interface.

-H

Previous Topic:	3rd Biannual Eclipse/OMG Workshop on March 25
Next Topic:	[CDO] Undo/Redo with CDO

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 04:10:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter