nope, session beans are used by only one client at a time, but why would you
want a SLSB to have a persisted handle anyway?
This would be best modeled with a Stateful Session Bean, and would be as
resource expensive as your current, SLSB-based pattern is
My 2c,
JP
-----Original Message-----
From: Vidur Dhanda [mailto:[EMAIL PROTECTED]]
Sent: Jueves, 09 de Noviembre de 2000 1:05
To: Orion-Interest
Subject: EJB SLSB Question
I can't find a _definite_ answer to my question. Hopefully, someone can
give me some pointers. Is it legal, per EJB 1.1, for multiple client
threads to access a SLSB? Here's why this is important for me.
Apparently, there is no portable way for a SLSB to tell a client that it
has timed out. Hence, if a client caches a SLSB, it is prone to some
"random" error. So, I figured, I will write a "keep-alive" thread and
wrap the SLSB in an application object as a delegate. And in the SLSB,
I will implement a no-op - ping(). Now, there's the possibility, that
the SLSB will be in a method call when the keep-alive thread decides to
do a ping. DO I need to guard against that?
Thanks,
Vidur
--
Vidur Dhanda
Active Solutions
tel: 617/566-1252
[EMAIL PROTECTED]
www.active-solutions-inc.com
