EJB G wrote: > > Can Session Beans be considered as realization of > each use case which in turn updates > model entity beans.
Yes, provided you don't insist that a session bean is one-to-one with a usecase. Sometimes you may choose to have one session bean handle several use cases, eg order entry and order modification; at the furthest extreme you may choose to have a single Session Bean to handle everything that users with a certain role (or set of roles) need to do, so that a Stateful session bean instance in effect represents a logged-in user. This is an attractively simple design for a small application. cheers... Ian ======================================== Ian McCallion Alexis Systems Limited Romsey, UK Tel: +44 1794 514883 Fax: +44 1794 501692 ======================================== =========================================================================== 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".
