Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339460

Summary: Generate and Execute EMF-based models in "Acore"
Product: [Modeling] AMP Reporter: Miles Parker <milesparker>
Component: AMFAssignee: Miles Parker <milesparker>
Status: NEW --- QA Contact: Miles Parker <milesparker>
Severity: enhancement    
Priority: P3 CC: jonas.ruettimann, mackerrow
Version: 0.9.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Miles Parker CLA 2011-03-09 23:51:49 EST 
Rather than (or perhaps in addition to) transforming EMF based models to AMF (Bug 325484), it seems like it makes more sense to allow EMF models to stay as Ecore and "advise" those models with AMF models. That would allow users of EMF based models (let's face it, a much larger set of users :)) to take advantage of AMF without losing the general focus. We'll do this in the following basic way -- details subject to change as we experiment.

1) Implementing AMF model for peers/advisors to Ecore models:
     a) AAgent <- SAgent for EClass.
     b) AAttribute <- SAttribute for EAttribute.

2) Implementing AMF Edit support for the difficult mapping between elements.

3) AMF Gen support, initially for generating ItemProviders as well as Adapter plumbing.

4) IDE integration to make the whole thing work with generated AMF models. (Yikes.)

I'm going to try to do this as an extension to metaabm, but I don't think that's going to work -- too much plumbing needs to change. I'm strongly leaning toward the more ambitious idea of biting the bullet and finally beginning "acore" proper on a very experimental basis. This will give us two threads.. a maintenance metaabm stable for Indigo release, and an acore release for bleeding edge adopters.

Oh, and I really would like to do this for EclipseCon. In a week and a half.