jatin,
of course you can cache a (remote) reference to the
_home interface_ of an entity/session (stateful or
stateless - doesn't matter) bean.
the home interface behaves like a (object instance) factory
and exists independent of any instance of a bean.
refer to the ejb 1.1 spec sections on the lifecycle/object
interaction diagrams of entity & session beans.
-krish
----- Original Message -----
From: Jatin Bhadra <[EMAIL PROTECTED]>
To: Krishnan Subramanian <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, May 18, 2001 5:13 PM
Subject: RE: Where to perform cached JNDI lookups
> Does this mean that you cache the Remote Reference to Home Object?
>
> For eg:
>
> Say Remote Reference to Home Object A of an EJB is cached.
>
> Client 1 gets the Remote Reference to Home Object A from cache and call
ejb
> create on it. This creats EJB object and Primary key. This primary key set
> to Entity Context And Entity Context is bound to Home Object.
>
> Now when Client 2 wants refernce same bean. It also gets the same Home
> Object back and when Client 2 call ejb create on Home Object, Entity
context
> of Client 1 will be overwritten.
>
> Correct me if I am completely wrong.
===========================================================================
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".
