Re: UML, EMF and EOF
Re: UML, EMF and EOF
- Subject: Re: UML, EMF and EOF
- From: Pierre Frisch <email@hidden>
- Date: Wed, 26 Nov 2003 07:05:40 -0800
Fridiric,
This is more a class template issue than anything else. I agree that
EOModeler should do it out of the box but you can very easily fix it by
using EOGenerator and building a good template. EOGenerator comes with
a lot of example and you can have your dream.
Pierre
On Monday, November 24, 2003, at 11:11 PM, DevReseune wrote:
Hi (4),
Yes, it's my last email (only for this evening).
A subproject of Eclipse is EMF for Eclipse Modeling Framework. It's a
powerfull project. As with EOF, EMF is a tool to build a data model.
But, where EOF manages only to-one or to-many relationship, EMF
manages container, inverse relationship and many other UML
abstractness. When I tell about inverse relationship, I know that EOF
can do that, but with a usefull method that isn't in the model. In
EMF, when you call setParent(newParent), EMF remove the object from
its previous parent, add it to the new and set this new parent. Only
we the call of setParent()! A better way, isn't it?
So, my question is: will Apple update EOF to use the same
fonctionality of EMF, or continue to use the new Cocoa paradigm to
manage relationship between objects, without a powerfull solution of
inverse relationship management, container solution, and many
contracts that in UML we can add to your model?
Frederic
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.