forum-omondo.com :: View topic - Creation of genmodel file modifies package name

logularjason · Joined: 17 Jan 2005 Posts: 3

When I create a new EMF class diagram, I enter the package name com.mycompany.domain. This creates the correct "name" attribute in the corresponding ecore file:

however, after Ormondo prompts me to create a genmodel file, the diagram indicates that it has been modified - saving the diagram updates the ecore file so that "name" only contains the last segment of the package:

Of course, any generated code is placed in the package "domain", not "com.mycompany.domain", as desired.

Why is Ormondo stripping off part of the package name - surely this is not desired behaviour?

I'm using the current free edition with eclipse 3.0.1 under fedora core 3.

julien · Site Admin Joined: 16 Mar 2003 Posts: 201

logularjason · Joined: 17 Jan 2005 Posts: 3

I'm surprised by the inability to allow fully qualified package names via the Omondo GUI - it seems to break the standard Java convention for avoiding namespace clashes of class names. Note that the Omondo GUI allows package names with dots to be entered, however it quietly drops the prefix at the genmodel creation step. This seems unsatisfactory.

Note that I can manually create EMF solutions with dots in the ecore "name" element as shown above - seems to work fine.

Simply specifying the package prefix in the genmodel file as you suggest doesn't work, because:

1) Even after I manually update the "Base Package" field in the genmodel file, files like plugin.xml still contain the erroneous data generated by Omondo (e.g. the class name is still domain.DomainPackage), and so the application won't run.

2) I don't get the genmodel file until *after* I've chosen "Generate Model" in Omondo. By this stage, code has been generated into the wrong package, so I need to delete this manually.

Wouldn't it be better for Omondo to accept package names with dots, as it does now, but to produce ecore, genmodel, and java files that are consistent with the users input? Seems like a bug to me.

logularjason · Joined: 17 Jan 2005 Posts: 3

Also, when Omondo ignores the package prefix, it produces a plugin ID that is not fully qualified, so it's susceptable to clashes with other folk's plugins.