Community
Participate
Working Groups
Currently there is only support for one metamodel (UML2). One Scenerio where support for other metamodels would be useful is with profiles. Defining a stereotype which extends extended metaclasses seems to work fine. However there is a problem applying the stereotype... See: http://dev.eclipse.org/newslists/news.eclipse.tools.uml2/msg04179.html
Created attachment 51961 [details] getEClassifier now considers any model stereotyped by EPackage getEClassifier now considers any model with EPackage stereotype. If none can be found it tries to use the UML EPackage.
Thanks! I've done a quick test with the patch with a slightly modified UML2 editor. And was able to apply the stereotype successfully.
Created attachment 54290 [details] patch for editor support to include types of extended metamodels.
Created attachment 54292 [details] Updated patch to UMLUtil
The fix has been committed to CVS.
The fix is available in build I200611231810.
*** Bug 173269 has been marked as a duplicate of this bug. ***
Created attachment 58717 [details] the stereotypes is emtyp for extended type
I have tested the 2.1M4. The getAppliedStereotypes() are always empty in my testcase. To run testcase, please proceed as following: 1. Generate the edit and editor plugins 2. run eclipse runtime workbench 3. Create a file using the wizard "FS model" 3. select "Folder" as root element 4. Save the editor 5. Rename the file extension in ".xmi" 6. Open the file with UML Editor 7. Load the FS.metamodel.uml resource 8. select the root folder, Call UML Editor Menu Package->Apply profile Select FS profile 9. Call UML Editor Menu Element->Apply Stereotyps the dialog has no stereotypes.
A correction in my previous post. It is the getApplicableStereotypes() returns empty, instead of getAppliedStereotypes().
What kind of file did you attach (I don't know how to open it)? Please attach your metamodel and profile (in UML2 format) so that we can investigate.
Created attachment 58726 [details] the applicable stereotype list is empty for extended metatype
Here is the attached jar, which contains metamodel and profile files.
Yves, the problem is that your metamodel is not stereotyped as an EPackage and hasn't been assigned a namespace URI. If you do so (in a development environment) and then (re)define the profile, it will use the appropriate metadata (from the package registry). I tried this (setting the namespace URI to http:///fs.ecore) and it worked for me.
Move to verified as per bug 206558.
