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.
JB.
Rickard �berg wrote:
> On Wed, 26 Jul 2000 12:32:26 +0200, Jean-Baptiste Nizet
> <[EMAIL PROTECTED]> wrote:
> >The simplest thing to do is to use the java:comp/env naming context of this bean
> >to store the properties. This will obviously work for read-only properties. But
> >can I be sure that the bean will be able to bind or rebind some values in this
> >context?
>
> No, the java: namespace is read-only.
>
> > And if it is able to do it, can I be sure that all the other instances
> >of the bean will automatically see these new values, or is the container allowed
> >to give each instance its own copy of the settings?
>
> The container can implement this anyway it pleases since it is
> read-only.
>
> >I tried it with IAS, and it seems to work well, but I wonder about other
> >servers.
>
> IAS is buggy then.
>
> regards,
> Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
> ===========================================================================
> 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".
