[news.eclipse.modeling.m2m] Re: [QVTO] How to handle optional attributes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]

[news.eclipse.modeling.m2m] Re: [QVTO] How to handle optional attributes with primitive types?

From: Alex <alex.leites@xxxxxxxxx>
Date: Wed, 16 Sep 2009 14:39:18 -0400
Newsgroups: eclipse.modeling.m2m
Organization: Eclipse Community Forums
User-agent: FUDforum

Depending on your use case (and level of control of the Ecore) you might also consider using attributes that are nullable instead of unsettable. These can be checked for null directly in QVT. For booleans use EBooleanObject instead of EBoolean, for enumerations this is done using an additional wrapper EDataType.

Alex

References:
- [news.eclipse.modeling.m2m] [QVTO] How to handle optional attributes with primitive types?
  - From: Mark Br?oerkens

Prev by Date: [news.eclipse.modeling.m2m] [QVTO] Accessing Ecore Feature Maps
Next by Date: [news.eclipse.modeling.m2m] Re: [QVTO] Accessing Ecore Feature Maps
Previous by thread: [news.eclipse.modeling.m2m] Re: [QVTO] How to handle optional attributes with primitive types?
Next by thread: [news.eclipse.modeling.m2m] [QVTO] Help on "SimpleUML to RDB" example
Index(es):
- Date
- Thread