[news.eclipse.tools.emf] Re: extending eType(s) -- just rethinking

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Ralf,

Comments below.

Ralf Buschermoehle wrote:
> Hi again(2),
>
> Ralf Buschermoehle wrote:
>
> > As far as I understood (now) ... you refered to add a new ecore 
> > package/edata type on level 1, generate the sources and extend/bind 
> > them to the API's covering the types (e.g. converters)? 
>
> As far as I understand now ... you were also refering to level 0 ...
Yes.  EcorePackage and XMLTypePackage aren't so special, except that 
they're directly available in the core runtime.
> > The problem then would be the dynamic generation of level 0 models - 
> > thus we don't have source code to extend - maybe one could use 
> > reflections at this point, but I think the extension of the emf 
> > sources would be simpler?
> But the dynamic generation problem persists ... right?
Dynamic models can use data types from generated models so you can 
provide a package that acts as a library of data types, just like 
XMLTypePackage does.
> Greetings,
>
>     Ralf