| Java element | Transformation output |
|---|---|
| Package | The transformation generates a package that
has the fully qualified name of the package that contains the Java elements to transform. Consider
the following Java code fragment:
packageB.packageC;
ClassAlpha{
}
The transformation generates the following UML
representation:
<package>packageB |
| Java implementation class |
|
| Java interface | In the target model, in the corresponding path
of the Java package, the transformation
generates a UML interface that has the same name as the Java interface. Depending on the target profile that you select in the transformation configuration, the transformation applies either the «ServiceInterface» stereotype from the Services Modeling (SoaML) profile or the «serviceSpecification» stereotype from the deprecated Software Services profile. |
| Java class | The transformation transforms only the Java classes that are Parameter
types in the methods of the interface that corresponds to the transformation
source. For these Java classes, in the target model, in the corresponding package path, the transformation generates a UML class that has the same name as the Java class. The names of the Java attributes do not change in the generated UML class. Consider the following Java class: Package a.b.c;
Import a.d.ClassB;
Import x.a.ClassD;
Class ClassA{
Int x;
String a;
ClassB c;
ClassD d;
}
For each attribute that is of type Java class, where the class exists in the workspace, the transformation creates a UML class, as in the following example: <package>a
<package>b
<package>c
<class>ClassA
<attribute>x //primitive type
<attribute>a // primitve type
<attribute>c //ClassB type
<attribute>d //ClassC type
<package>d
<class>B
<package>x
<package>a
<class>ClassD
|