Restrictions on the CORBA Service
Restrictions on IDL Compilation
The IDL compilation can be used with the following products:
•Interstage Application Server Enterprise Edition
•Interstage Application Server Standard Edition
•Interstage Application Server Plus
Table 2-8 Restrictions on IDL Compilation
No | Restriction | Alternative | Date of |
|
| Method | Removal |
|
|
|
|
1 | None | Not | |
|
|
| determined |
|
|
|
|
2 | A prototype module definition file with no | None | Not |
| named |
| determined |
| COBOL mapping of IDL files. |
|
|
|
|
|
|
3 | Long long overflows are not checked when IDL is | None | Not |
| compiled |
| determined |
|
|
|
|
Restrictions on C and C++ Programming
C and C++ Programming can be used with the following products:
•Interstage Application Server Enterprise Edition
•Interstage Application Server Standard Edition
Table 2-9 Restrictions on C and C++ Programming
No. | Restriction | Alternative | Date of |
|
| Method | Removal |
|
|
|
|
1 |
| Use _exit() | Not |
| When a child process is generated by a server | when you finish | determined |
| a child process |
| |
| application, and the child process is terminated by exit(), | only. |
|
| the parent process is also terminated. |
|
|
2 |
| None | Not |
| If WS Compilers C++ 6 used, no context object can be |
| determined |
|
|
| |
| used. |
|
|
|
|
|
|
3 |
| None | Not |
| A context cannot be used on the C++ application. |
| determined |
|
|
| |
|
|
|
|