I prefer to treat the EJB as one component. Since the different parts
always interact in the same manner, I find no reason to show that
behavior in every diagram. If you seek completeness, my idea is to keep
a separate abstract model defining that scope.
/Marcus
[EMAIL PROTECTED] wrote:
>
> I have been creating the UML models for an application that uses EJBs (both
> session and entity EJBs). I am unsure whether to add all of the associated
> interfaces (EJB Home and EJB Remote) to the sequence diagrams.
>
> For completeness, I would prefer to do this, but for simplicity, as well as
> making reasonably sized diagrams, I feel that it may just be overkill.
>
> Are there any "standards" that people use when doing UML models for apps
> which incorporate EJBs?
--
Marcus Ahnve email: [EMAIL PROTECTED]
Lecando AB Office: +46-(0)8-634 94 18
Sweden Mobile: +46-(0)70-462 19 18
www.lecando.com ICQ#: 4564879
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
