----- Original Message -----
From: Assaf Arkin <[EMAIL PROTECTED]>
> > Could you additionally address dan's point from a later message that is
> > related to this, viz:
> > > It is hard for me to believe that synchronize is not allowed (even as
wrappers around
> > > code within method calls). For example suppose that I have created a
multi-safe data
> > > structure using synchronize. Are you saying that I cant use that
data structure
> > > within the bean? Surely some of the jdk datastructures have
synchronized methods.
> > Does this mean, for example, that I cannot use Hashtable or Vector in my
> > bean classes?
> Yes you can, as long as they are not shared between two threads.
So in fact a bean *can* use third party classes that use synchronization
primitives, even though the specification says it cannot. I find this
interesting.
> If you use a Vector or Hashtable from one thread and something happens
> to your thread inside the synchronized stuff, your Hashtable/Vector
> might be corrupted. But you shouldn't care. IF something happens to your
> thread, the EJB server will discard that bean (always).
Is this not an argument for allowing users (knowing they run a risk) to
create threads? Granted and fully understood: a user may create a thread
that could do some damage. So what?
Cheers,
Laird
===========================================================================
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".
