Typically, the transformation transforms associations the same way as the UML to Java transformation: it transforms the endpoint attributes into Java properties.
If an endpoint of the association is a class with an <<Entity>>, <<Service>>, or <<MessageProcessor>> stereotype, the transformation does not transform that endpoint. Instead, the transformation writes a message to the log file in the metadata directory that states that the endpoint property was not transformed. The exception to this occurrence is when the association is between two classes with <<Entity>> stereotypes and both classes are generated as CMP 2.x beans. Then, the transformation transforms the UML association into an EJB 2.0 relationship, which is also known as a container-managed relationship (CMR). The following table illustrates the mappings between association properties and EJB relationship properties:
Association property |
EJB relationship property |
End1 |
BeanA |
End2 |
BeanB |
End1 name |
BeanB CMR name |
End2 name |
BeanA CMR name |
End1 navigability |
BeanB navigability |
End2 navigability |
BeanA navigability |
|
|
|
|
The following figure illustrates two UML classes with <<Entity>> stereotypes. The association between the classes is generated into a CMR if the transformation generates both entity classes as CMP 2.x entity beans.
After the transformation occurs, the deployment descriptor has an entry to describe the CMR between AEntity and BEntity. As the following figure illustrates, the project's deployment descriptor can display the association between the two CMP 2.x entity beans:
Terms of use | Feedback
(C) Copyright IBM Corporation 2004. All Rights Reserved.