39 lines
2.3 KiB
HTML
39 lines
2.3 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Initial context support</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><a name="jndiicr"></a>Initial context support</h5>
|
||
|
|
|
||
|
|
|
||
|
|
<p>All naming operations begin with obtaining an initial context. You can view the initial context as a starting point in the name space. Use the initial context to perform naming operations, such as looking up and binding objects in the name space.</p>
|
||
|
|
|
||
|
|
<p>The default initial context depends on the type of client. Here are the different categories of clients and the corresponding default initial contexts:</p>
|
||
|
|
|
||
|
|
<!--<p><strong>WebSphere Application Server - Express JNDI interface implementation</strong></p>
|
||
|
|
|
||
|
|
<p>The JNDI interface is used by EJB applications to perform name space lookups. WebSphere Application Server clients by default use the WebSphere Application Server CosNaming JNDI plug-in implementation. The default initial context for clients of this type is the server root of the server specified by the provider URL.</p>
|
||
|
|
|
||
|
|
<p>For example, if a naming client specifies an application server name service port in the provider URL, the server root is the context root. If a naming client specifies a node agent name service port in the provider URL, the node root is the context root.</p>-->
|
||
|
|
|
||
|
|
<p><strong>WebSphere Application Server JNDI interface implementation prior to V5.0</strong></p>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server clients running in releases prior to WebSphere Application Server V5.0 by default use WebSphere Application Server's V4.0 CosNaming JNDI plug-in implementation. The default initial context for clients of this type is the cell persistent root, also known as the legacy root.</p>
|
||
|
|
|
||
|
|
<p><strong>Other JNDI implementation</strong></p>
|
||
|
|
|
||
|
|
<p>Some applications can perform name space lookups with a non-WebSphere Application Server - Express CosNaming JNDI plug-in implementation. Assuming the key NamingContext is used to obtain the initial context, the default initial context for clients of this type is the cell root.</p>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|