--- "Shun, Vadim" <[EMAIL PROTECTED]> wrote:
> Per my understanding of EJB, it is highly
> undesirable for client to
> communicate directly to the entity bean. It is
> preferrable whenever possible
> to use session beans (stateless if possible) that
> will hold the connection
> with entity beans. You can say you are using
> Mediator pattern to achieve
> ultimate decoupling and utilize the best performance
> in component driven
It depends. Say, you want list and show all people's
recode: their names, address.... and allow user to
modify them. There is hardly any business logic there.
A CMP Entity Bean is good enough.
If you have business logic, and/or access more than
one table, a Session Bean is the choice.
=====
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
===========================================================================
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".
