Bug 150177 - Should be able to use dynamic EMF instead of the generated code to store underlying diagram model
Summary: Should be able to use dynamic EMF instead of the generated code to store unde...
Status: RESOLVED FIXED
Alias: None
Product: GMF-Tooling (ARCHIVED)
Classification: Modeling
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: 2.1   Edit
Assignee: Artem Tikhomirov CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2006-07-10 12:51 EDT by Alex Shatalin CLA
Modified: 2010-07-19 22:19 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Shatalin CLA 2006-07-10 12:51:34 EDT 
Currently generated diargamming code works only with the model code generated by EMF. Would be nice to have a possibility to generate code working with dynamic EMF feature. Use case:
1. Create .ecore domain meta-model (code was not generated for this .ecore model)
2. Create .gmfmap model
3. Transform .gmfmap-> .gmfgen
4. Generate code

Generated code should be able to load specified .ecore meta-model, create new instance of corresponding model using dynamic EMF/load it from the specified model file, create new diagram feasible to visualise this model.

I think, there should be an option in .gmfgen model "Use dynamic EMF" and different code should be generated in these two different situations.
Comment 1 Artem Tikhomirov CLA 2006-07-10 13:24:21 EDT 
"Dynamic EMF" is the term EMF's Developer Guide book uses to refer to the provided implementation of reflective API. Though 'Dynamic' is often percieved as something that is being contantly modified. Not sure 'dynamic' is most exact term here, as the use-case is about the frozen meta-model, one that can't be changed in run-time. Perhaps, 'codeless model' term would better describe the intention - don't generate the code, use EMF's reflective API to access meta-model.
Comment 2 Richard Gronback CLA 2007-03-01 10:56:12 EST 
Updated target milestone
Comment 3 Anthony Hunter CLA 2007-05-01 09:22:28 EDT 
Since GMF 2.0 M6 was released April 5, 2007, doing a bulk move of all open Bugzillas currently on M6 to 2.0 M7. Owners will need to access if the issue really is targetted for 2.0 M7.
Comment 4 Artem Tikhomirov CLA 2007-06-18 09:10:42 EDT 
Bulk update, descoping from 2.0
Comment 5 Artem Tikhomirov CLA 2008-02-28 15:38:43 EST 
Basic functionality to work with dynamic models was delivered. 
Few configuration issues as well as tests pending.
Comment 6 Artem Tikhomirov CLA 2008-02-29 10:14:35 EST 
Note, dynamic meta-models may need to get registered using dynamic_package extension point from EMF

<extension point="org.eclipse.emf.ecore.dynamic_package" >
   <resource uri="http://example.org/Example" location="model/Example.ecore#/"/> 
</extension>
Comment 7 Artem Tikhomirov CLA 2008-06-05 07:48:30 EDT 
Tests added into RuntimeCompilationTest.
Comment 8 Eclipse Webmaster CLA 2010-07-19 22:19:46 EDT 
[GMF Restructure] Bug 319140 : product GMF and component
Generation was the original product and component for this bug