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 objects | Bound 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 #2 | Session Bean home object | java: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 interface | java: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] |
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 (,).