JaMoPP Parser combined with Java2UML Reactions leads to Exception

[SofiaAnanieva]

The JaMoPP parser does not create package elements, but instead only adds a prefix to all compilation unit names. Consequently, when using the JaMoPP parser and executing Java2UML reactions, the packages are not propagated to UML and the following exception occurs:

java.lang.IllegalStateException: The object org.eclipse.uml2.uml.internal.impl.ClassImpl@f4e74b0 (name: String, visibility: public) (isLeaf: false, isAbstract: false, isFinalSpecialization: true) (isActive: false) is part of a correspondence to [[org.emftext.language.java.classifiers.impl.ClassImpl@15cf976f (name: String)], [org.emftext.language.java.containers.impl.CompilationUnitImpl@7b667c59 (name: java.lang.String.java) (namespaces: [java, lang])]] but not in any resource

There are two options to circumvent this error and propagate packages correctly:

1. After creating the Java model instance with JaMoPP, packages must be added manually, similar to the following test case: https://github.com/vitruv-tools/Vitruv-Applications-ComponentBasedSystems/blob/a75[…]/applications/umljava/tests/java2uml/JavaToUmlPackageTest.xtend

2. package-info.java files are placed in every package. The reactions process these files to create respective UML packages, even without package elements in the Java model instance.

A possible fix could be to adapt the reactions and have them create containing packages during class transformations.