Relationship of namespaces java:comp/env and local:
 Technote (troubleshooting)
 
Problem(Abstract)
Can local: be used in place of java:comp/env?
 
Resolving the problem
There are multiple java: comp/env name spaces inside a server. java: name space bindings are things like enterprise bean (EJB™) Homes and resources, which are IndirectJndiLookup objects.

There is a single local: name space in each server and it contains bindings for all the resources and local enterprise beans. The java:comp/env IndirectJndiLookup is redirected to the local: name space in the case of resources or local enterprise beans, but is redirected to the CosNaming name space in the case of non-local enterprise beans. The result is that local: is not exposed to the users, but is used only internally.

The local: name space is an internal WebSphere Application Server implementation; the java:comp/env name space is the J2EE™ programming model.

In conclusion, local: cannot be used in place of the java:comp/env name spaces when doing a lookup.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > JNDI/Naming
Operating system(s): Windows
Software version: 6.1.1
Software edition:
Reference #: 1180620
IBM Group: Software Group
Modified date: Sep 29, 2004