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?
Please note that this requires that multiple clients be able to concurrently
access the object with the object itself providing the necessary
synchronization. It appears that session EJBs don't allow concurrent access
(they throw a remote exception).
I also am told that EJBs are not allowed to do custom synchronization (e.g.
don't make any wait() or notify() calls). Is this true? Isn't this overly
restrictive?
===========================================================================
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".
