Bugzilla – Full Text Bug Listing
| Summary: | [EWL] GMF integration should expose variable for referring to GMF notation model | ||
|---|---|---|---|
| Product: | [Modeling] Epsilon | Reporter: | Louis Rose <louis> |
| Component: | Core | Assignee: | Antonio Garcia-Dominguez <agarcdomi> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | abhijit.gurav, agarcdomi, dkolovos, louis, ruicag |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | interim | ||
|
Description
Louis Rose
*** Bug 325160 has been marked as a duplicate of this bug. *** Fixed in SVN r2420, in a somewhat roundabout way. Many EMF model editors (such as the ones generated by GMF) use an EditingDomain that inherits from the EMF AdapterFactoryEditingDomain, which stores the ResourceSet being edited. Therefore, we can do a checked downcast of the EditingDomain and expose the Resource objects different from the "Model" one as additional in-memory EMF models. I've decided to name each of these additional models from their file extension. For instance, a ".spdiag" resource will be exposed as "Spdiag". If we have more than one ".spdiag" resource, the second one will be "Spdiag2" and so on. I'll revise the examples a bit now. I've extended the .ewl file for the flowchart example so it includes several wizards that change the notation model: http://dev.eclipse.org/svnroot/modeling/org.eclipse.epsilon/trunk/examples/org.eclipse.epsilon.eugenia.examples.flowchart.extensions/flowchart.ewl Fixed in the latest interim version. Fixed in version 1.2. |