Bouml reference manual - Fedora Project Packages GIT repositories

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html317 of 378 07/10/2007 15:55In BOUML the generated code is obtained by the substitution of macros in a text, the macros known by the Java code generator are :${comment} is replaced by the artifact description adding /* */${description} is replaced by the artifact description without adding /* */${package} is replaced by the package xx forms, dependent on the package specifications associated to the BOUML packagecontaining the deployment view where the artifact is defined.${import} is replaced by import forms specified by dependencies stereotypes import from classes produced by the artifact to classesor packages.${definition} is replaced by the definition of the classes associated to the artifact.@{xyz} is replaced by the user property value in case xyz is the key of this property. The property if searched first for the artifact, ifnot found for the deployment view containing the artifact, if not found in the package containing the deployment view etc ...ClassThe Java definition of a class is set through the Uml, Parametrized, Instantiate and Java tabs of the class dialog.A Java type definition may be a class, an interface or an enum (may be defined through a class), depending on the stereotype andtranslation in Java (see generation settings).In BOUML the generated code is obtained by the substitution of macros in a text, the macros known by the Java code generator are :${comment} is replaced by the description of the class adding /* */${description} is replaced by the class description without adding /* */${public} produce public when the class is declared public${final} produce final when the class is declared final${abstract} produce abstract when the class is abstract${name} is replaced by the class's name