Closed barais closed 11 years ago
If you have only abstract model elements, you'll never have concrete elements to load or serialize... As you can not create model element instances of an abstract type, you'll never have anything to serialize.
Unless you link your different metamodels to the abstract metamodel (by inheritance), in order to obtain one big metamodel.
Exactly
2013/4/23 Brice Morin notifications@github.com
Unless you link your different metamodels to the abstract metamodel (by inheritance), in order to obtain one big metamodel.
— Reply to this email directly or view it on GitHubhttps://github.com/dukeboard/kevoree-modeling-framework/issues/31#issuecomment-16869974 .
Do you mean you have, (1) in concrete metamodels, model elements that extend some of the Abstract metamodel; or (2) the abstract metamodel is composed by gathering abstract elements from several metamodels (containing concrete elements) ? In the first case I'm not sure about what we can do if we do not start from the concrete metamodel. In the second, we may follow the EMF proxies to generate also the linked elements...
Managed since 1.6.0 - for abstract classes impl are not generated but stilll interfaces are for typing purpose .
If I create a metamodel with only abstract classes to modularize some concepts between several metamodels. Kotline generator does not generate the ModelSerializor class.