If all you are doing with your entity beans is persisting state, then
perhaps there is no need to use entity beans. However, if your entity beans
have business logic, can you get that with JDO? Even accessing all entity
beans through session bean facades does not mean that the entity beans
will/should have no logic of their own.
Componentization and reuse would be another reason to use entity beans. If
you persist objects without out using entity beans, I expect that every
developer is more likely to recode the object persistence as needed. Without
entity beans you are relying on code reuse, not component reuse. It seems to
me that entity beans represent a better encapsulation and location mechanism
that just relying on class files.
Some of the same entity bean performance issues can be rasied about session
beans. Obviously you don't have the performance issues related to database
synchronization. But you still have network communication, object lookup,
and container performance overhead. If you were to make your session bean
functionality too fine grained performance would suffer.
Rick Hansen
The views, opinions, and judgments expressed in this message are solely
those of the author. The message contents have not been reviewed or
approved by West Group.
> -----Original Message-----
> From: Anup Maliyackel [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 26, 2001 1:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Entity beans vs DAO(Data Access Objects)
>
>
> Hi
> After going through so much discussion there are a few things that lie
> still unresolved
>
> 1."Entity beans should be ideally accessed through Session
> beans"- This is
> what all the Ejb gurus say. If that is the case, why make entity beans
> remote objects at all?. The answer that some app.servers
> might optimize
> remote calls to local calls when the beans are co-located(i.e
> in the same
> VM) is side-stepping this issue.
> 2. Since Entity beans are supposed to be accessed from a
> Session bean(The
> "facade" pattern) why do we have separate transaction
> attributes for Entity
> beans- these attributes could be controlled from the Session
> Bean itself.
> 3."Another function of Entity beans is persistence". The persistence
> mechanism for Enitity beans in EJB1.1 was fairly crude. The EJB2.0
> addresses some of these issues,but it is yet to be finalized. It might
> bring forth other issues. See
> http://www.onjava.com/pub/a/onjava/2001/02/28/ejb.html.
> Regards
> Anup
>
>
===========================================================================
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".
