 Types of an UML profile are not recognised [message #643377] |
Mon, 06 December 2010 16:56  |
 Tom Brandenburg
Messages: 58
Registered: October 2010
Location: Abstatt, Germany |
Member |
|
|
Hello,
since my current project got to big to post a small extract here I take a simple example, representing my current problem.
Imagine that you have written a workflow which reads in an UML model, transforms it to another model and generates code out of the transformed model. The workflow lays in its own plugin, which uses other plugins for the transformation and the generation. For defining the UML model I need a profile. The profile should also lay in its own directory:
plugin.workflow
|
+- metamodel
|
+- someMetaModel.ecore
+- model
|
+- model2BeRead.uml
+- workflow
|
+-main.mwe
plugin.umlprofile
|
+- profile
|
+- someProfile.profile.uml
plugin.transformation
|
+- ext
|
+- someExt.ext
plugin.generation
|
+- xpt
|
+- someXpt.xpt
I assign the profile to the model2BeRead with "Load resource...". Eclipse then inserts relative paths to the profile in the model2BeRead-file. Now the simple problem is that transformation does not recognise types like someProfile::someStereotype, name is null and so on. If I move the profile to plugin.workflow, load and apply it again, then it works and types are recognised. Like here:
plugin.workflow
|
+- metamodel
|
+- someMetaModel.ecore
+- profile
|
+- someProfile.profile.uml
+- model
|
+- model2BeRead.uml
+- workflow
|
+-main.mwe
But I don't want to have this, because then there are cyclic dependencies in my project.
Since it works in the second case I think my workflow should work and that it is something different.
Does anyone have an idea?
Thanks in advance and best regards
Tom
[Updated on: Mon, 06 December 2010 16:59] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.02432 seconds
] 
Search
Help
Register
Login
Home
