Ripan Bansal wrote:
>
> It is documented in the EJB1.1 Spec that from inside the stateful and
> stateless session beans access to "java:comp/env" environment naming context
> is allowed. What is the significance of this context?
java:comp/env can be thought of as one specific JAVA COMPonent's ENVironment
variables. That is, it's how the app server provides a specific set of
environment variables to a specific component, or how the surrounding
environment parameterises the component. Obviously, being JNDI, it's a bit more
powerful that a mere set of name-value pairs, but that's the idea.
Use of JNDI for this is consistent with an admirable trend in the java world of
not having two mechanisms when one will do, which is why it replaced Properties
that were used by EJB 1.0 vendors.
java:comp/env could in theory be provided by any type of container, eg a servlet
container, a web browser for applets, and even by the JVM itself for Java
applications. I think we may see some of these in the future. (Perhaps someone
else can tell us that the future is already here!)
Ian McCallion
Alexis Systems Limited
Romsey, UK
===========================================================================
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".
