>
> You're right. I finally found it in the specs (p. 202) :
> Enterprise bean instances are not allowed to modify the
> bean's environment at
> runtime.
>
> Do anyone know why? Since the environment is only accessible
> by the bean instances, I
> don't see why we would have to protect the bean from itself.
>
1. Synchronization. If read/write access is allowed, then any access (read
or write) has to be serialized. Slow.
2. Clustering. How do you propagate changes to the environment to all
servers in a cluster? Suppose one of them is down right now?
- Avi
--
s/\be(\w+)/e-\1/g;
===========================================================================
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".
