|
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 |
|
|
|
|
|
|