Use EMF for domain modelling

soundasleep / iaml

Automatically exported from code.google.com/p/iaml

3 stars 1 forks source link

Use EMF for domain modelling #242

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What new or enhanced feature are you proposing?
Currently the domain metamodel uses a custom DomainSchema/DomainAttribute 
framework. This should be changed to use the Ecore framework.

What goal would this enhancement help you achieve?
This is a recognised sub-goal of issue 234: Implement metamodel changes as 
discussed in metamodel review

Original issue reported on code.google.com by soundasleep on 28 Apr 2011 at 1:03

Blocking: #234, #232, #217
Blocked on: #251

GoogleCodeExporter commented 9 years ago

Original comment by soundasleep on 28 Apr 2011 at 1:11

GoogleCodeExporter commented 9 years ago

Original comment by soundasleep on 28 Apr 2011 at 1:11

GoogleCodeExporter commented 9 years ago

Started in r2725.

Original comment by soundasleep on 29 Apr 2011 at 7:08

Changed state: Started

GoogleCodeExporter commented 9 years ago

Restarted in r2783.

Original comment by soundasleep on 3 May 2011 at 4:32

GoogleCodeExporter commented 9 years ago

Original comment by soundasleep on 3 May 2011 at 7:16

GoogleCodeExporter commented 9 years ago

Perhaps model completion should be used to automatically create new types, 
rather than inserting them in manually as in r2789.

Original comment by soundasleep on 4 May 2011 at 1:58

GoogleCodeExporter commented 9 years ago

XSD data type integration completed in r2797.

Original comment by soundasleep on 4 May 2011 at 4:51

GoogleCodeExporter commented 9 years ago

Resolved in r2818.

Original comment by soundasleep on 6 May 2011 at 2:49

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Original comment by soundasleep on 16 May 2011 at 6:00