standard.class UML Class

03 class 1

Keys:

1 The Java Class button is used to indicate that the Class will be taken into account by Java Architect. When checked, the UML Class becomes a Java Class and thus its relevant fields appear.
2 The Java Annotation button is used to indicate that the Class will be taken into account by Java Architect as an annotation declaration. When checked, the UML Class becomes a Java Annotation and thus its relevant fields appear.

javaclass Java Class

03 class 2

Keys:

1 A real-time preview of the generated code.
2 The UML name field is used to modify the UML name of the Class, i.e. the name that appears in the model browser.
3 The Alias tick-box is used to indicate that the class will use an alias for the generated file. This can be useful if the UML name of the Class is not compatible with the java naming rules. When checked, a new field used to enter the alias name appears on the right.
4 The Visibility buttons are used to indicate the visibility of the class.
5 The Modifiers tick-boxes are used to indicate the modifiers which will be generated in the class signature.
6 The Annotations field is used to add metadata for the class. Example: @Entity, @Deprecated.
7 The Javadoc field is used to enter a javadoc content for the class.
8 The Java Class tick-box is used to indicate that the Class is a Java element, i.e an element that is taken into account by the Java Architect module. Unchecking it will make it a simple UML element.
9 The No code field is used to indicate that the Class will not be generated.

javaannotation Java Annotation

03 class 3

Keys:

1 The UML name field is used to modify the UML name of the annotation type, i.e. the name that appears in the model browser.
2 The Alias tick-box is used to indicate that the annotation type will use an alias for the generated file. This can be useful if the UML name of the Class is not compatible with the java naming rules. When checked, a new field used to enter the alias name appears on the right.
3 The Documented tick-box adds @Documented for this annotation type, making it part of the public API of annotated elements.
4 The Retention policy drop-list is used to choose how long annotations with the annotated type are to be retained.

  • SOURCE: annotations are to be discarded by the compiler.

  • CLASS: annotations are to be recorded in the class file by the compiler but need not be retained by the VM at run time.

  • RUNTIME: annotations are to be recorded in the class file by the compiler and retained by the VM at run time, so they may be read reflectively.
5 The Inherited tick-box adds @Inherited for this annotation type, making it automatically inherited by sub-classes of annotated elements.
6 The Target tick-boxes are used to indicate the contexts in which an annotation type is applicable.

  • Package: package declaration

  • Type: class, interface, annotation type or enum declaration

  • Annotation: annotation type declaration

  • Module: module declaration.[1]

  • Field: field declaration (includes enum constants)

  • Method: method declaration

  • Constructor: constructor declaration

  • Parameter: parameter declaration

  • Local variable: local variable declaration

  • Type parameter: type parameter declaration.

  • Type use: any use of a type.
7 The Visibility buttons are used to indicate the visibility of the Annotation type.
8 The Annotations field is used to add metadata for the Annotation type.
9 The Javadoc field is used to enter a javadoc content for the Annotation type.
10 The Java annotation tick-box is used to indicate that the Class is a Java element, i.e an element that is taken into account by the Java Architect module. Unchecking it will make it a simple UML element.
11 The No code field is used to indicate that the Class will not be generated.
1. Requires at least Java 11.