Avi Kivity wrote:
> >
> > 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?
>
These are serious issues, but they would be solved by the container, not by the
bean provider. But you're right that it would perhaps decrease the performance
significantly.
Anyone know of a server providing the exact same kind of JNDI context, but which
could be shared between components?
JB.
>
> - 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".
--
Jean-Baptiste Nizet
[EMAIL PROTECTED]
R&D Engineer, S1 Belgium
Kleine Kloosterstraat, 23
B-1932 Sint-Stevens Woluwe
+32 2 200 45 42
===========================================================================
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".
