2.2.1 Naming management functionality

The naming management manages the name and storage location of an object (EJB home objects, business interface references, and J2EE resources corresponding to the Enterprise Beans). By using the naming management functionality, the EJB client is able to use the necessary objects from the names of the Enterprise Beans or resources to be invoked, without knowing their storage locations.

Also, when you use a resources adapter compliant with the Connector 1.5 specifications, the objects to be managed are also managed by the naming management. The objects to be managed are the objects used for sending and simultaneously receiving messages from within the J2EE application. For details on the objects to be managed, see 3.16.5 Looking up Administered objects.

In the JNDI of the naming management functionality, the objects other than the CORBA object references (RMI-IIOP remote objects and JDBC data source objects) are handled as follows:

The naming management functionality provided with Application Server includes the functionality provided in J2EE with Application Server-specific enhancements and the functionality that is unique to Application Server. To determine whether the functionality is unique to Application Server, see 1. Application Server Functionality.

The following table describes the relation between the naming management functionality provided by Application Server and the target objects.

Table 2-2 Relation between the naming management functionality provided by Application Server and the target objects

FunctionalityEnterprise BeanJ2EE resource
EJB home objectBusiness interface
Binding and looking up objects in the JNDI name spaceYYY#1
Looking up with the Portable Global JNDI namesYYY
Looking up with names beginning with HITACHI_EJBYYN
Assigning an optional name to the Enterprise Beans or J2EE resources (user-specified name space functionality)YYY
Searching the CORBA Naming Service by using the round-robin policyYYN
Caching objects with the naming management functionalityYN#2N
Switching the CORBA Naming ServiceYNN
Legend:
Y: Available
N: Not available
#1: The names beginning with HITACHI_EJB cannot be looked up.
#2: If the J2EE server is restarted by setting the ejbserver.jndi.cache property to "on" while a business interface is being used, a javax.ejb.EJBException might occur when the business method is executed.

Note
When a custom error page is set up in a Web application, you cannot use the JNDI from the set error page.