| |
Home About Us A-Z Index Search • |
Organization | AT&T Laboratories -Cambridge Limited |
---|---|
Author | Sai-Lai Lo |
Product Identification | Version/Release Number | Product Supplier | |
---|---|---|---|
1. | omniORB | 2.7.1 | AT&T Laboratories - Cambridge |
Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details | |
---|---|---|---|---|---|
1. |
|
| None. | Test Report from Test Suite | Test Suite:
VSORB 1.1.0b Test Report: Pass |
Question 1: Does the product interpret or ignore pragmas for RepositoryID formats?
Response
Pragma | Product Behavior |
---|---|
ID Interpreted ? | Yes |
prefix Interpreted ? | Yes |
version Interpreted ? | Yes |
Question 2: Does the product require interface-specific pragmas to precede an Interface body?
Response
Question 3: Does the product require interface-specific pragmas to precede an operation declaration?
Response
Question 4: Which object adapters does the product supply?
Response
Adapter | Supported |
---|---|
Basic Object Adapter (BOA) | Yes |
Portable Object Adapter (POA) | No |
Question 5: Do DII routines return a status code?
Response
No
Question 6: Does the product use the period character to partition the name space?
Response
No
Question 7: Does this implementation support the Interface Repository?
Response
No
Question 8: Which language mappings does the product support?
Response
Mapping | Supported |
---|---|
C | No |
C++ | Yes |
Java | No |
Smalltalk | No |
Cobol | No |
Ada | No |
Question 9: Can the implementation take advantage of templates if they are supported by the target environment?
Response
Yes
Question 10: Can the implementation's IDL-to-C++ translator support 64-bit integer types?
Response
No
Question 11: For which target environment can the implementation's IDL-to-C++ translator provide a mapping for module?
Response
Environment | Mapping | Supported |
---|---|---|
namespace is supported | Module is mapped to C++ namespace | Yes |
namespace is not supported, nested classes are supported | Module is mapped to C++ classes | Yes |
namespace and nested classes are not supported | Module is mapped like C mapping | No |
Question 12: For which exception handling environments can the implementation's IDL-to-C++ translator provide a mapping?
Response
Mapping | Supported |
---|---|
Real C++ exception handling is supported | Yes |
Real C++ exception handling is not supported | No |
Question 13: How does the product map the IDL interface construct?
Response
Not Applicable.
Question 14: For which IDL types other than union does the product provide an explicit mapping?
Response
Question 15: Which constant handling environments can the implementation's IDL-to-COBOL translator support?
Response
Environment | Supported |
---|---|
Constants are supported by the COBOL compiler | Not Applicable |
Constants are not supported by the COBOL compiler (and are propagated by the IDL compiler) | Not Applicable |
Question 16: Which COBOL environments can the implementation's IDL-to-COBOL translator support for mapping basic data types?
Response
Environment | Supported |
---|---|
Basic data types are mapped to COBOL Typedefs | Not Applicable |
Basic data types are mapped to COBOL COPY files | Not Applicable |
Question 17: What additional rules does the product provide for resolving name space clashes?
Response
Question 18: Does the implementation use strings associated with Exception_Message and Exception_Information in the package Ada.Exceptions to ``carry'' exception members?
Response
Not Applicable
Question 19: Is access to CORBA services tasking-safe?
Response
Not Applicable
Question 20: Does the implementation support tasking-safe operations?
Response
Not Applicable
Question 21: Conformance with IIOP Version 1.0 is required. Support for IIOP Version 1.1 is optional. Does this implementation support the optional IIOP Version 1.1?
Response
No
The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.