On Fri, 14 Jul 2000 11:16:24 -0700, Nicholas Whitehead
<[EMAIL PROTECTED]> wrote:
>Obviosuly this will work, but I belive that this will
>soon be a legacy interface. Additionally, other than
>redeploying the beans, you cannot change these
>settings.
>
>This is in contrast to JNDI entries where you can
>easily change values at runtime without redeploing
>your beans.
Good point. So, one way to introduce what you are referring to would be
to allow JNDI-links to be defined in the deployment descriptor.
For example, let's say I defined a link "foo" in the java:-namespace to
the global JNDI-name "myapp/settings/foo". Then my bean could look up
the value with new InitialContext().lookup("java:comp/env/foo"), and I
could change the value for all beans needing that setting by doing new
InitialContext().rebind("myapp/settings/foo", "somenewvalue").
The notion of references already exists in EJB 1.1 deployment
descriptors, so it wouldn't be that different from what is already
there. It would mean that the java:-namespace implementation supports
links though, but that might be an ok requirement anyway.
Opinions?
/Rickard
--
Rickard �berg
@home: +46 13 177937
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".
