Dear Chip, I feel U have missed the point behind sequence diagram. Actually U can show the Home Interface and Remote Interface as one instance called "container system instance". The create(), remove() or bussiness_method() can first be called on this so called "container system interface" which can be further shown to call the subsequent method in the bean instance. U may have a look at the diagram below. Yeah, the "container system instance" instance will be created by the container. Believe me the container implements these interfaces and instantiates them as well when ever U invoke a method. This will give a clear picture of actually what is happening. <<...>> Thanks, Rashid Khan Chip Wilson <[EMAIL PROTECTED]> wrote: 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".
