This has irritated me in some ways. If you place values in <env-entry>'s and you want to change them, you have to redeploy the bean! It seems strange to link the environment entries in that way... even though some EJB containers can be smart on redeployment. For items that need to be updated, applications use another area to store these values (db, flat file, jndi, etc).
D > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]]On Behalf Of Victor Langelo > Sent: Monday, November 19, 2001 8:25 PM > To: [EMAIL PROTECTED] > Subject: Re: context java:comp/env is read only > > > It's mandated by the EJB spec. See section 20.2.4 of the EJB 2.0 spec. > > --Victor > > Raymond Blum wrote: > > > Hi there > > I'm using WebLogic 6.1 and and having problems trying to bind values to > > the context "java:comp/env" > > I look up that context through my initial context, retrieve values from it > > that were coded in my <env-entry>, but when I then try to bind some names > > and values to the context I get an "OperationNotSupportedException" with the > > message "bind not allowed in a ReadOnlyContext" > > > > Is this a security policy issue? Can anyone help? > > > > Thanks > > ---Raymond > > =========================================================================== > 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". > =========================================================================== 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".
