Bouml reference manual - Fedora Project Packages GIT repositories

More documents

Recommendations

Info

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html316 of 378 07/10/2007 15:55Java generatorThe Java code generator is a plug-out directly written in C++.The generated sources follows the definition made in BOUML at the artifact / class / operation / relation / attribute / extra member levels.When the code generation is applied on a artifact associated to several classes, the code generation is made for all these classesNevertheless the the Java code generator produce first the code in memory and update the appropriate files only when it is necessary, tonot change the last write date of the files for nothing. Depending on the toggle verbose code generation of the global menu Languages thecode generator is verbose or not.The Java code generator plug-out may be called on :a class : in this case the code generation is in fact applied on the class's artifact, then on all the classes associated to this artifacta artifact : in this case the code generation is in fact applied on all the classes associated to the artifacta class view : the code generation will be applied on all the sub classes, then on all the artifacts associated to these classesa deployment view : the code generation is applied on all the sub artifactsa package (may be the project itself) : the code generation will be applied on all the sub class views and deployment views, then onall their sub classes and artifacts.When the Java code generator is ask through the Tools menu, it is applied on the project, then on all the artifacts.The name of the generated files depend on the artifact name, the extension depend on the language and is fixed for each by thegenerationssettings(see below), the directory where the files are generated may be set in each package containing directly or indirectly the artifact (seegeneration directory).artifactThe Java definition of a artifact is set through the Java source tabs of the artifact dialog.The code generation depend on the stereotype of the artifact :text : the Java definition of the artifact is produced without changes, the name of the generated file is the name of the artifact,including the extension.source : see below.else nothing is generated for the artifact.The generated file name is the artifact's name with the extension specified in the first Java tab of the generations settings :
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
Page 1 and 2:
file:///C:/uml/BOUML/bouml_3.0/doc/
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266: file:///C:/uml/BOUML/bouml_3.0/doc/
Page 315: file:///C:/uml/BOUML/bouml_3.0/doc/
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
show all

Bouml reference manual - Fedora Project Packages GIT repositories

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?