Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "TigerstripeF2f 20080421 EMF"
| Line 2: | Line 2: | ||
== EMF Migration == | == EMF Migration == | ||
| + | |||
| + | ===Plan=== | ||
| + | The purpose of the EMF migration is to transition from using a proprietary Metamodel implementation in the core Tigerstripe to using EMF instead. | ||
| + | This transition will be conducted in phases: | ||
| + | * First develop an EMF-based metamodel | ||
| + | * Use the EMF-Persistence layer to read/write Tigerstripe models using the current file format, and model reference scheme. | ||
| + | * Validate this API | ||
| + | * Integrate the EMF based implementation into Workbench. | ||
| + | |||
| + | ===Background=== | ||
| + | The core of Tigerstripe is built around the concept of an "Artifact Mgr" that indexes a model in various way and provides an API to the UI, diagrams and generators. | ||
| + | The art. mgr has evolved overtime into a very complex and difficult to maintain component. | ||
| + | |||
| + | It will be replaced with a "ModelRepository" that will hold an EMF model, support facets, and address cross-model references. | ||
| + | |||
| + | ===Action Items=== | ||
| + | For the [[Tigerstripe_0.3_stream|0.3]] release we are mainly focusing on the getting the Tigerstripe EMF API up and running. Without attempting to integrate it to the workbench yet. | ||
| + | |||
| + | To that end we will need to address: | ||
| + | |||
* Finish persistence to POJOs (JS) | * Finish persistence to POJOs (JS) | ||
* Redo proxy resolution (ED) | * Redo proxy resolution (ED) | ||
* Clean up meta-model (RC) | * Clean up meta-model (RC) | ||
* JUnit testing for all of above | * JUnit testing for all of above | ||
Latest revision as of 11:10, 23 April 2008
< To: TigerstripeF2F_20080421
EMF Migration
Plan
The purpose of the EMF migration is to transition from using a proprietary Metamodel implementation in the core Tigerstripe to using EMF instead. This transition will be conducted in phases:
- First develop an EMF-based metamodel
- Use the EMF-Persistence layer to read/write Tigerstripe models using the current file format, and model reference scheme.
- Validate this API
- Integrate the EMF based implementation into Workbench.
Background
The core of Tigerstripe is built around the concept of an "Artifact Mgr" that indexes a model in various way and provides an API to the UI, diagrams and generators. The art. mgr has evolved overtime into a very complex and difficult to maintain component.
It will be replaced with a "ModelRepository" that will hold an EMF model, support facets, and address cross-model references.
Action Items
For the 0.3 release we are mainly focusing on the getting the Tigerstripe EMF API up and running. Without attempting to integrate it to the workbench yet.
To that end we will need to address:
- Finish persistence to POJOs (JS)
- Redo proxy resolution (ED)
- Clean up meta-model (RC)
- JUnit testing for all of above