| Package merging [message #626304] |
Sun, 30 March 2008 06:34 |
Eclipse User |
|
|
|
Hi,
I'm having some beginner issues with UML2 package merging - maybe
somebody can help me out and give me a kick-off...
I'm trying to develop a DSL based on UML Activities. So, the plan is to
create a UML model, add Package Merge relations to the basic,
fundamental and intermediate packages of the UML::Activities package,
merge, transform to Ecore, and then add a couple of elements to the
resulting ecore model. The resulting model should optimally have no
dependencies on other models.
So I imported o.e.uml2.source into my workspace and copied the
Superstructure.uml and Infrastructure.uml models to my project. First
problem: Both files do have problems when I validate them (things like
"Not all members of namespace foo are distinguishable within it.", "The
context of subsetting property... does not conform with the subsetted
property...") - is that fine? I'm using Europa 3.3.2...
Next, I added the 3 Package merge relations and validated: fine. After
mergíng sucessfully, I validated the resulting .uml file, and discovered
1 problem: "Not all members of namespace foo are distinguishable within
it." Sounds familar...
If I now transform to Ecore (no errors), I get 3 .ecore files:
InfrastructureLibrary.ecore, UML.ecore and foo.ecore. Why is my
foo.ecore files depending on the other models? I expexted to just get
foo.ecore.
Finally, the resulting .ecore models contain validation errors: a couple
of properties are contained in the super- as well as in the subclass.
Obviously, the generated code doesn't compile.
For me it looks like there's already something messed up with the
original .uml models, but that's somehow hard to believe :-) I'm
probably making some stupid mistake. Anybody?
Thanks in advance,
Chris
|
|
|
Powered by
FUDForum. Page generated in 0.03043 seconds
Home