> From: Peter Donald [mailto:[EMAIL PROTECTED]]
>
> > So reentrant implies threadsafe. (But not the other way around.)
>
> Only in sensible systems ;) EJBs are not thread safe but can
> be reentrant ;)
To end this nitpicking of a nitpicking (nitpickings are not safe in
mailing list threads, and may not be re-entered), just a quick note
to those who read this and wonder just what the **** we're on about:
http://www.jguru.com/faq/view.jsp?EID=788123
Actually, you have confused concurrency control and "re-entrant" -
re-entrant is something different
Nick Minutello, Mar 10, 2002
The Re-entrant field has nothing to do with concurrency and
threading
[...which is the way Peter used it...]
(though, thread-safety is usually what re-entrant implies).
[...which is what I said...]
The re-entrant flag is there to allow loop-back calls on an entity
bean.
it is best illustrated by an example: If there are 2 entity beans A,
B, and there is a call made on beanA which calls a method on beanB
which in turn makes a call on beanA, you effectively have a
loopback.
Now, if re-entrant is not set, the container will throw an exception
at this point. If re-entrant is set, the container will permit the
loopback call.
(...)
> I was only putting it in so that Paul if he wanted to use it
> in EOB. However I
> don't think it will be useful in containers that are not
> focused on biz
> objects. (ie all the other containers).
OK, in that case - keep it.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
