By default, all calls from Client to EJB Bean/Server will be remote calls
(i.e. going through the client stub, making network call, etc.). When you
refer to "caching" this is typically done within the Bean within the EJB
Server, not necessarily caching the data on the Client. Thus, caching data
within the Entity Bean to prevent constantly having to read attribute data
from the underlying persistent data source.
That being said, some vendor implementations (Persistence PowerTier EJB
being one of them) offer the option of passing EJB contents by value, which
would allow you to have access to the Entity Bean attributes without having
to make the remote call. This seems to reflect the type of "client caching"
you are looking for.
mike mc
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Lisa Retief
> Sent: Tuesday, July 20, 1999 4:09 AM
> To: [EMAIL PROTECTED]
> Subject: Accessing cached data on the client
>
>
> Hi all,
>
> Just a quick question. If an EntityBean (for example Person) has a data
> member "surname" cached when created, then if a client should call
> getSurname() on the remote interface, will this call involve a remote
> lookup, or will it refer to the *_ServiceStub.class for the cached
> information.
>
> Thanks in advance, Lisa
>
> ==================================================================
> =========
> 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".
>
===========================================================================
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".
