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.
Entity beans were not designed merely for object persistence, and there
are better approaches for that. They were designed to put some business
methods on top of your data objects.
arkin
Steve Roth wrote:
>
> 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".
