Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » UML2 » Re: UML -> Ecore (Derived + Composite)
Re: UML -> Ecore (Derived + Composite) [message #627597] Tue, 19 May 2009 01:17
Ed Merks is currently offline Ed Merks
Messages: 25746
Registered: July 2009
Senior Member
JT,

Yes, the UML converter is intentionally designed to do that. Best to
ask about it on the UML newsgroup which I've added to the "to" list of
the reply.


John T.E. Timm wrote:
> In attempting to recreate the Supplier / PurchaseOrder example from
> "EMF FeatureMaps", I ran into an issue where if I define a property in
> UML to be Composite and Derived, only derived is carried through to
> Ecore (during model import) which causes problems in serialization. If
> I change this attribute in the resulting Ecore after import,
> serialization works fine. From the article, preferredOrders and
> standardOrders should be composite, derived, transient, volatile,
> ordered, and unique.
>
> Thanks,
>
> JT
>
Previous Topic:Datamodel migration with ecore2ecroe
Next Topic:Re: UML -> Ecore (Derived + Composite)
Goto Forum:
  


Current Time: Sat Apr 19 11:42:28 EDT 2014

Powered by FUDForum. Page generated in 0.02629 seconds