This section describes the constraints on using the container extension library and server start and stop hook functionality.
- Application portability
The container extension library functionality is not included in the J2EE specifications. Therefore, when the container extension library is used, the portability of the application is reduced.
- Invoking the container extension library
The container extension library is presumed to have been invoked from the servlets, JSPs, and Enterprise Beans. Note that the following usage forms cannot be applied:
- Referencing the EJB-JAR files and WAR files from the container extension library and server start and stop hook functionality (including the classes of the EJB-JAR files and WAR files inheriting the container extension library class).
- Using the J2EE container functionality from the container extension library and server start and stop hook functionality (invoking the APIs such as the Enterprise Beans, JNDI, and JDBC).
- Referencing the server start and stop hook functionality directly from the classes of the EJB-JAR files and WAR files (including the classes of the container extension library inheriting the classes of the EJB-JAR files and WAR files).
- Accessing the files and directories
Do not operate the following files and directories from the container extension library and server start and stop hook functionality:
- Files and directories beneath the Cosminexus installation directory
- Files and directories beneath the J2EE server work directory
- Using the JNI functionality
When the JNI functionality is used from the container extension library and server start and stop hook functionality, the processing with the native method cannot be managed with the J2EE server. For example, if a memory access violation occurs in the native method, the J2EE server terminates abnormally in each JavaVM process.
- Using Cosminexus TPBroker
- The server functionality of Cosminexus TPBroker cannot be used with the container extension library and server start and stop hook functionality. This is because the CORBA objects of Cosminexus TPBroker cannot be activated on the J2EE server.
- The DII functionality of Cosminexus TPBroker cannot be used.
- Using the installation type option package
Do not use the container extension library and server start and stop hook functionality as the installation type option package. The installation type option package is the file placed in the following directories:
- The JAR file placed in Cosminexus-installation-directory\jdk\jre\lib\ext
- The native code binary placed in Cosminexus-installation-directory\jdk\jre\bin
- Registering the shutdown hook
Do not register the shutdown hook with the container extension library and server start and stop hook functionality.
- Setting up the handler function (in Windows)
When you use the container extension library for setting up the handler function of a process in Windows, do not execute operations such as returning TRUE, performing the DLL end processing, and terminating a process by invoking functions such as ExitProcess with the handler function that processes the CTRL+BREAK signal.
The J2EE server and the other programs that use Component Container might not operate.
- C++ library (in Linux)
If the container extension library is implemented using C++ in Linux, that library must be built with Red Hat Enterprise Linux 4 or later. A C++ library built with Red Hat Enterprise Linux 3 cannot be executed.