Assaf Arkin wrote:
>
> Seesion beans are modeled after your business process, while entity
> beans are modeled after your business data. And so both will include
> business logic in their method calls.
First, I agree with you in principle.
However, I'd make the argument a little differently, so as to rely as
little as possible on fuzzy terminology. (After all, postalCode may be
a business datum, and validate() may be a piece of business logic, but
who is to say that validating a postal code is not an example of a
business process?)
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?
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".
