-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
> My understanding of EJB
> 1) Put business logic in session beans. Session beans operate on entity
> beans.
Minor correction: put *inter* bean business logic in session beans, or
business logic that requires some specific transaction semantics.
> 2) Persistent objects are entity beans. They do not contain very much
biz
> logic. They are kind of dumb!
Minor correction: go ahead and put business logic in an entity bean provided
that it affects that bean only and the transaction semantics are OK.
> Peter Coad's modeling examples of moment-interval (e.g. SaleToCustomer)
> contain numerous business logic method declarations. Because of all the
> intelligence of this object, it would be modeled as a session bean in EJB.
It might. It might not.
> However, a moment interval such as a SaleToCustomer is something we would
> want to persist to a database, thus it would be an Entity bean. So what
is
> a SaleToCustomer, an very smart entity bean?
Probably, yes. I recognize that I'm unorthodox in my views here. :-)
Cheers,
Laird
===========================================================================
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".
