EJB3 and Class/Component diagram

Hi All!

Could anybody advice the rigth place for <<Session Bean>> stereotype in Class/Component diagrams? For instance, there is one session bean interface, corresponding implementatiion class and several POJOs which are used from this implementation. All these classes and interface are shown in Class Diagram and as single component (with realization classes inside) in Component Diagram. Where stereotype should be shown - in class diagram, in component diagram for realization class or for whole component?

By the way, could anybody advice a good example of Component Diagram with EJB3?

Thank you in advance!
Rob

You can include a << Session EJB >> stereotype for each class is part of the EJB, e.g. interface class and implementation class. Classes of objects that use the EJB should not have the stereotype. The stereotype should be shown were it makes the most sense. You should include it wherever you feel it is appropriate.

If you have used EJB 3, Annotations and UML Stereotypes are similar concepts. You can apply Stereotype where you use Annotation.

Thanks, but what about component diagram? Should EJB stereotype be applied to whole component or to particular realization class inside component?

Rob Rider wrote:Thanks, but what about component diagram? Should EJB stereotype be applied to whole component or to particular realization class inside component?

I'm not sure what you mean by realization class.
About component, you may have a component that contains many Session Beans and apply <<Session Bean>> Stereotype.
Or maybe a component can be a Session Bean (a component can represent a single class), then you can apply <<Session Bean>> Stereotype.

Anyhow, don't get lost, the very reason of applying Stereotypes is for making the diagrams clearer, more understandable, and more specific, if you think in that way, you should know better how you should apply Stereotypes.

Thanks, Kengkaj. It's more clear now.

Rob