Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Epsilon » [Eugenia] Problem with tool.name annotation detail by using different metamodel
[Eugenia] Problem with tool.name annotation detail by using different metamodel [message #590670] Thu, 15 July 2010 09:27
Eclipse User
Originally posted by: mario28988.yahoo.de

Hi newsgroup,

I have created the following metamodel which extends the general ecore
metamodel:

example
|- DiagramElement -> EClass
|- ModelElement -> EClass
|- EditorProject -> EPackage

Based on this metamodel I have created a model with gmf annotations:

Editor Project TestProject
|- gmf

|- Model Element AModelElement
|- name : String
|- gmf.node
|- label -> name
|- tool.name -> NewToolName

|- Diagram Element ADiagramElement
|- gmf.diagram
|- ownedModelElements : AModelElement
|- gmf.link
|- tool.name

My Problem is, that if I generate the gmf models via eugenia only the
tool name of the link element will be changed (not the node tool name).
Referring to this I checked the Ecore2GMF.eol script of the
org.eclipse.epsilon.eugenia plugin and located the problem in the
createCreationTool operation. The condition of the if statement 'if
(element.isTypeOf(ECore!EClass) and element.isNode())' always returns
false, because the element type isn't exactly EClass but AModelElement
(which is derived from EClass). However, the isTypeOf method returns
false. :-(

Is this behaviour a problem of the isTypeOf method or should the
implementation of the Ecore2GMF.eol be different? Does anyone know the
location of the eol api reference according to this?

What would you advise me in this issue? What's a 'good' solution for
this problem?

Thanks in advance.

Mario
Previous Topic:[Eugenia] Problem generating the Diagram.
Next Topic:[Eugenia] Problem with tool.name annotation detail by using different metamodel
Goto Forum:
  


Current Time: Wed Jul 23 00:01:00 EDT 2014

Powered by FUDForum. Page generated in 0.01564 seconds