2.4.2 Automatically bound objects

With Application Server, the standard application name, standard module name, and EJB reference are automatically bound to the names defined in Java EE. Note that the standard application name and standard module name are defined on Application Server as follows:

The following table describes the automatically bound objects and names.

Table 2-10 Automatically bound objects and names

Bound objectsBound names
Standard application name (java.lang.String type)java:app/AppName#1
Standard module name (java.lang.String type)java:module/ModuleName#1
EJB reference #2Session Bean home objectjava:global[/standard-application-name]/standard-module-name/Enterprise-Bean-name[!fully-qualified-class-name]
java:app/standard-module-name/Enterprise-Bean-name[!fully-qualified-class-name]
java:module/Enterprise-Bean-name[!fully-qualified-class-name]
Session Bean business interfacejava:global[/standard-application-name]/standard-module-name/Enterprise-Bean-name[!fully-qualified-class-name]
java:app/standard-module-name/Enterprise-Bean-name[!fully-qualified-class-name]
java:module/Enterprise-Bean-name[!fully-qualified-class-name]
#1
Can be looked up only from an EJB-JAR or Web application.
#2
With the EJB 3.1 specifications, the class name omission format in which the fully-qualified class name is omitted can be used for lookup when there is one EJB reference (home object and business interface) for one Enterprise Bean.
Furthermore, with Application Server, the reference registered first can be looked up using the class name omission format in the following order of priority even if there are multiple references:
1. Remote home object
2. Local home object
3. Local business interface (including when the business interface is omitted)
4. Remote business interface
However, we do not recommend lookup in the class name omission format because the specifications related to the class name omission format for multiple references are not provided in Java EE.

If an object that can be looked up with a name beginning with HITACHI_EJB exists in an application, you can also use the Portable Global JNDI name for lookup.

Note that when the application starts, the Portable Global JNDI name is output to message KDJE47701-I for each bound EJB reference. When the class name or application name omission format of the Enterprise Bean is enabled, all the formats that can be looked up are enumerated using comma and space delimiters (,).