Hello Luo,
> I know that in some design patterns entity beans are not exposed
to the client tier. My problem is that in such case, why should we use
entity beans. We can use DAO intstead and also can avoid the overhead of
the inter-bean calls. Any tip is appreciated.
We use Entity Beans for three reasons:
1) concurrent access from clients, that means shared data
2) transaction and security stuff
3) abstraction from database
Especially 3) is quite interesting for some companys. For example insurance
companies or banks in germany have to "histories" their data. When a
customer changes his address you are not allowed to override the old one.
You have to insert a new record. A lot of projects implement their own
historisation. But when you can reuse entity which encapsultes these
mechanism, e.g. insert sql statement and not update sql statement in
ejbStore, a lot of work is done.
But do NEVER access entity beans from the web tier.
regards,
--
[EMAIL PROTECTED]
MATHEMA Software GmbH
N�gelsbachstra�e 25 b
91052 E r l a n g e n
D e u t s c h l a n d
Tel +49(0)9131/8903-0
Fax +49(0)9131/8903-55
http://www.mathema.de
===========================================================================
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".
