----- Original Message -----
From: "Anup Maliyackel" <[EMAIL PROTECTED]>
> 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.
Agreed, but isn't nice that they *can* be remote, especially in failover
situations or when isolation is needed? If you choose to deploy them together,
then you get the intra-VM optimizations. If not, then you don't. I like the
flexibility as long as it doesn't impact performance.
> 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.
I have always agreed with you on this matter. Early on, I had wanted to mark my
entity beans as "Supports" and let the Session Beans drive the transaction boat.
However, many containers will not let you mark an entity bean with these vague
transaction attributes. The spec refers to these situations as "undefined." I
believe they are firming this up in EJB 2.0.
> 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.
Crude yes, but cruder than what? This first iteration of JDO will be probably
lack many of the features of products such as Cocobase or TopLink. I don't use
much CMP and if JDO proves to be robust enough, I may use it to persist my
entity beans. I have a feeling that extensions to EJB 2.0 may allow me to
overcome the two most lacking issues in BMP entity beans (IMHO):
1. Requirement of n+1 queries on Finders, and
2. Lack of PreparedStatement caching.
Once I get these, I'll be happy.
jim
===========================================================================
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".
