> 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.
===========================================================================
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".
