Sequence diagrams depict messages between instances. Sometimes a class can be shown, to indicate a constructor call or static method call. Since interfaces cannot have concrete implementations and cannot be instantiated, I can't think of any reason to include them on a sequence diagram. >From: [EMAIL PROTECTED] > >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? > >Joe > >=========================================================================== >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". > _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. =========================================================================== 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".
