1.2.1 EJB container functionality

The following table describes the functionality of an EJB container. Select the functionality according to the purpose of the system. For details on the functionality, see the Reference location column.

Table 1-2 Correspondence between the EJB container functionality and the purpose of the system

FunctionalityPurpose of the systemCompliance with the Java EE StandardReference location
ReliabilityPerformanceOperation and MaintenanceExtendibilityOthersStandardExtended
Executing an Enterprise Bean----------YY2.2
Checking the compliance with EJB specifications----------YY2.3
Mapping of CMP field and data types----------YY2.4
Registering a reference in the JNDI name space of the EJB container#------Y--YY2.5
Connecting to an external resource------Y--Y--2.6
Transaction management in an Enterprise Bean----------YY2.7
Cache models of an Entity Bean (Specifying the commit option)--Y------Y--2.8
Managing the Pool of Stateless Session Bean, Entity Bean--Y------YY2.9
Controlling the access to the Enterprise BeansY--------Y--2.10
Setting up a timeout in the EJB container--Y------YY2.11
Timer Service functionality----------YY2.12
Invoking the remote interface of EJB--Y------YY2.13
Fixing the communication ports and IP address of the EJB container (TPBroker options)Y----------Y2.14
Using the default interceptor----------YY2.15
Omitting the local business interface (using No-Interface view)----------Y--2.16
Asynchronous invocation of a Session Bean----------Y--2.17
Specifying in the annotation of the Session Synchronization----------Y--2.18
Using a Singleton Session Bean----------Y--2.19
Legend:
Y: Supported
--: Not supported
Note:
The functionality for which Y is specified in both the Standard and Extended columns of the Compliance with the Java EE Standard column indicates that functionality unique to Application Server has been added to extend the functionality beyond the Java EE standard functionality. The functionality for which Y is specified only in the Extended column indicates functionality unique to Application Server.
#
This is implemented by using naming management.