If the Entity attributes are not volatile (i.e. not changing very
frequently, fairly static) then passing the Entity Bean by value to the
Client actually presents a good option.
//vendor
Persistence PowerTier for EJB gives you the option to set which attributes
can be accessed by value, which can be accessed by reference, etc. allowing
for a flexible approach based on how often certain Entity attributes are
changing.
//vendor
mike mc
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Lisa Retief
> Sent: Wednesday, July 21, 1999 12:15 AM
> To: [EMAIL PROTECTED]
> Subject: Allowing client to access cached data without RMI call - is it
> possible?
>
>
> Hi,
>
> I have a need to make certain methods within an EntityBean
> available to the
> client application (such as set() and get() methods on cached data,
> validate() on cached data) without invoking a remote network
> call. In order
> to do this would I have to send the actual Entity Bean instance to the
> client? This seems like a horrible solution to me - are there any
> suggestions? I hope I am missing something.
>
> 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".
