Donald Edgar wrote:
>
> > We need to write objects that contain transient (non-presistent) data that
> > needs to be shared among multiple clients. My understanding of stateful
> > session EJBs is that they are meant to be instantiated and used by a
> single
> > client. What kind of EJBs should we use to implement a shared object --
> for
> > instance an EJB that implements shared cache of some kind?
> >
>
> One technique we've used succesfully to share 'session beans' between
> multiple clients is to construct entity beans, with no persistent state,
> using well known primary keys. Singleton's can easily be constructed in this
> manner by declaring a pk with no attributes.
>
> regards,
>
> Donald.
>
But where does the transient shared data go, when the container decides
to remove your entity bean instance from memory? Maybe I'm missing
something but wasn't the problem sharing transient data? Maybe I
misunderstood the spec but I thought that there was no way to influence
whether a bean instance is kept in memory or not? If that is correct the
so-constructed Singleton would lose its state when being removed from
memory.
Please correct me if I'm wrong.
Regards,
Robert
--
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
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".
