If you rerun the UML-to-Java transformation or the UML-to-EJB transformation, the changes that you make to the source model affect previously generated code.
Model change | Impact on generated code | Impact of rerunning the transformation |
---|---|---|
Class or interface | Add implementation or extension | Clauses are rewritten or removed |
Class or interface | Remove implementation or extension | Clauses are rewritten or removed |
Dependency | Add | Import statement is added |
Enterprise bean class or interface | Add | No change |
Enterprise bean class or interface | Remove | No change |
Enterprise bean CMP field | Rename | Field with the previous name is retained Field with the new name is added |
Field | Move | Field in the previous location is removed Field is added in the new location |
Field | Rename | Field with the previous name is removed Field with the new name is added |
Method | Modify return type | Method return type is updated |
Method | Modify signature | Method with the previous signature is removed Method with the new signature is added |
Method | Move | Method in the original location is removed Method is added in the new location |
Method | Rename | Previously generated method is removed Renamed method is added |
Nested class or interface | Rename | Previously generated class or interface is removed New class or interface is added |
Nesting class or interface | Rename | File overwrite option of the UML-to-Java transformation determines
whether or not the previously generated Java™ file is deleted New Java file is created |