Wednesday, May 2, 2001 09:41 AM
I wish I had a quick answer for you, but the real answer lie in the activities of the JSR 26 committee. This group is currently working on a formal extension (profile) to the UML for modeling EJBs. I've seen some draft work, but can't say with any authority what the final outcome will be.
With that comment aside, I'd suggest that you model relationships with associations, and draw them in class diagrams. Component diagrams, are only suitable for expressing dependencies (a weak form of relationship).
Associations are used to model the concept of an instance maintaining a relationship to another instance. A dependency just shows that the class is dependent on another element. That is, if the interface changes or something like that, as opposed to a state change in the dependent object.