My understanding is that entity beans are meant to be components that
may realize parts of design models encompassing more than a single
class. Now, this sounds fine in the abstract, but what are the concrete
consequences? Let me put it like this:
- Taking the usual multi-tier stuff for granted, what are the specific
influences of EJB on design?
- What strategies are there to allocate domain objects to entity beans?
- What strategies are there to allocate functionality to session beans?
(Is it reasonable to represent Jacobson's "control classes" through
session beans?)
TIA,
Michael
===========================================================================
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".
