Re: [emf-dev] EMF metamodel reuse

[Ed Merks <ed.merks@xxxxxxxxx>]

Antoine,

Of course I'll continue tell people not to extend Ecore.  See https://bugs.eclipse.org/bugs/show_bug.cgi?id=252501 for the bitter complaints from those who don't follow that advice.  My advice would be to annotate Ecore, rather than extending it (much like one can annotate Java or XML Schema without extending it).  ExtendedMetaData and BasicExtendedMetaData show the approach for how Ecore was augmented but not extended to better address XML Schema mapping.  So, if you see appealing things in Ecore, reuse them, but don't extend them.  E.g., define your own Annotation class and feature to reference it; reuse EStringToStringMapEntry if you like. 

Of course I can't make people follow my advice, but I'm certainly quite able to ignore complaints about lack of binary compatibility for Ecore's impl classes. :-P

The advice of using the newsgroup is good. :-)

Cheers,
Ed


Antoine Toulme wrote:

An UTBM dude ! I'm from the UTT originally myself. Try the emf newsgroup for questions like this. Look up the BPMN modeler metamodel, we use the ecore metamodel to reuse EModelElement and some other cool things.

Thanks,

Antoine

On Wed, Feb 4, 2009 at 11:02 AM, hilaire <vincent.hilaire@xxxxxxx> wrote:

Hi all,


i'am searching a way to reuse and extend, if possible, the EMF metamodel
to design my own metamodels and produce graphical editors in the end.



Thank you



Vincent
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev

_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev