> In general, processes that don't gain anything by being broken down
> further, and that pertain to one type of object, should in most cases be
> exposed as entity bean methods. Processes that are more complicated
> than this and that involve more than one type of object should normally
> be exposed as session bean methods (and session beans as a whole since
> session beans themselves model processes; not just their methods).
>
> How's that?
Fair. I think that once you're past reading the spec and getting to
actual development, it becomes very clear what is session bean, what is
entity bean and how to best mix them. No hands-on experience can
substitute a specification (even if your writing is clearer than mine).
arkin
>
> 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".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
