> However, what about for business logic tied directly to a single table? For
> example, a PurchaseOrder Entity bean might expose a number of business
> methods.
>
> Are there any technical reasons why a Session bean would be preferable in
> this case?
in my mind, no. I think it's a misguided notion that entity beans are mere data
containers and should contain only getter and setter methods. I put actual
business logic in my entity beans. I find it cumbersome to put business logic
in a session bean when it makes perfect sense to put it in an entity bean.
cheers,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.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".
