Steve,
I our best practices work we are treating Entity Beans as clusters of domain
objects, having both persistence and domain logic. We use Session Beans as a
coarse grained interface facade and transaction control layer.
Regards,
-Chris.
> -----Original Message-----
> From: Steve Roth [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, February 04, 2000 9:58 AM
> To: [EMAIL PROTECTED]
> Subject: Entity vs. Session for Business Logic
>
> We're trying to identify the appropriate location in an EJB design for
> placing lower-level business logic.
>
> Reading various books and specs (J2EE) often leaves the impression that
> business logic goes in Session beans and Entity beans are for persistence
> only.
>
> For high-level business logic affecting multiple persistence tables, I can
> see this point.
>
> 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? (BTW-- we're using BMP for the Entity beans)
>
> Thanks!
> -Steve Roth, [EMAIL PROTECTED]
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
