If you specify EJB 3.0 elements in the Package Explorer view instead of using the Transformation Configuration editor, the source elements that you select override the source project or elements that are specified in the transformation configuration. The transformation configuration is not affected and the source that you specify on the Source and Target page of the transformation configuration editor or in the New Transformation Configuration wizard does not change.
A valid transformation target is a UML model, project, or folder in a project.
If the deployment descriptor does not contain the information to generate the required UML elements or stereotypes, the transformation uses the JPA annotations in the Java code.
The EJB 3.0-to-UML transformation uses the comparing and merging functionality to determine the differences between the target model and the temporary model that the transformation generates. When you run the transformation, the merge editor displays the differences between the two models. In the merge editor, you can select the changes that the transformation merges into the target model.
You can use the filters in the merge editor to show or hide the different types of deltas that occur when you run the Java-to-UML transformation. To simplify the view in the merge editor, click the Filters icon on the toolbar, and select the filters to apply.
For example, the transformation does not set upper and lower bounds when it transforms multiplicity elements such as attributes and parameters. In the temporary model, upper and lower bounds are set to null if no collection type is generated. If the upper and lower bounds are explicitly specified in the target UML model, even if these boundary values specify a default multiplicity of 0..1, a delta exists between the temporary model and the target model. For large models, these trivial deltas might be numerous, and make other deltas more difficult to see in the merge editor. To hide this type of delta, select the Filter out Trivial Lower and Upper Bound Changes filter.
In UML sequence diagrams, items such as topics, queues, and data sources do not contain information about their physical location. As part of reconciled modeling, when the EJB 3.0-to-UML transformation transforms these elements into UML, the transformation might create them in a target location that is different from their original location in the UML model because they do not contain information about their physical location.
The EJB 3.0-to-UML transformation might also generate extra usage relationships in the model instead of in the correct location in the sequence diagram.
The EJB 3.0-to-UML transformation does not generate relationships from entity beans.
The transformation provides integration functionality with IBM® Rational® Team Concert, CVS, Rational ClearCase®, and Rational ClearCase LT version control systems, which enables you to automatically check out files or add new files. You must enable team capabilities to work with configuration management systems.