Don Bate wrote:
> The term I usually use is a "role" for the name of the class.
> One has to be careful with these objects or one can end up with a
> process-oriented design.
Well, when you're dealing with transactional systems that cross many
object boundaries, I don't see how you can avoid a process-oriented
design. Having said that, my general rule is: business logic that
affects one entity bean only goes in that entity bean; business logic
that affects many entity beans goes in a session bean.
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".
