| |
| | |
Home • About Us •A-Z Index• Search • | |
| Organization | ThinkOne Inc. |
|---|---|
| Author | Arno Puder |
| Product Identification | Version/Release Number | Product Supplier | |
|---|---|---|---|
| 1. | MICO | 2.2.7 | ThinkOne |
| Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details | |
|---|---|---|---|---|---|
| 1. |
|
| None. | Test Report from Test Suite | Test Suite:
vsOrb Test Report: submitted journal file |
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 |
Rationale
These directives must be interpreted (yes) or ignored (no).
Question 2: Does the product require interface-specific pragmas to precede an Interface body?
Response
Rationale
Implementations are allowed to require such pragmas.
Question 3: Does the product require interface-specific pragmas to precede an operation declaration?
Response
Rationale
Implementations are allowed to require such pragmas.
Question 4: Which object adapters does the product supply?
Response
| Adapter | Supported |
|---|---|
| Basic Object Adapter (BOA) | Yes |
| Portable Object Adapter (POA) | Yes |
Rationale
This information is of use to server developers.
Question 5: Do DII routines return a status code?
Response
No
Rationale
Conforming CORBA implementations are not required to return this status code. Conforming implementations are required to specify which Status behavior is supported.
Question 6: Does the product use the period character to partition the name space?
Response
No
Rationale
Implementations are allowed to use the period (.) for partitioning the name space.
Question 7: Does this implementation support the Interface Repository?
Response
Yes
Rationale
The implementation is required to document this optional behavoir.
Question 8: Which language mappings does the product support?
Response
| Mapping | Supported |
|---|---|
| C | No |
| C++ | Yes |
| Java | No |
| Smalltalk | No |
| Cobol | No |
| Ada | No |
Rationale
A product registered as conformant to the CORBA Product Standard must offer one or more conforming language mappings.
Question 9: Can the implementation take advantage of templates if they are supported by the target environment?
Response
Yes
Rationale
Use of templates is not required, nor is it disallowed.
Question 10: Can the implementation's IDL-to-C++ translator support 64-bit integer types?
Response
Yes
Rationale
An alternative mapping is defined for integer types in 64-bit environments.
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 |
Rationale
Several alternative mappings are defined.
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 |
Rationale
Two alternative provisions are defined in the C++ mapping.
Question 13: How does the product map the IDL interface construct?
Response
Not Applicable.
Rationale
Conforming implementations are free to use any of these methods.
Question 14: For which IDL types other than union does the product provide an explicit mapping?
Response
Rationale
Implementations may chose to provide both implicit and explicit mappings for types in addition to union, such as structs and sequences.
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 |
Rationale
Constants are not supported in pure ANSI 85 COBOL.
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 |
Rationale
Typedef is an optional extension to ANSI 85 COBOL and may not be supported by all COBOL compilers.
Question 17: What additional rules does the product provide for resolving name space clashes?
Response
Rationale
The defined mapping defines a set of rules, but they cannot guarantee name clashes will not occur. Implementations may implement additional rules to further resolve clashes.
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
Rationale
The implementation is required to document this fact.
Question 19: Is access to CORBA services tasking-safe?
Response
Not Applicable
Rationale
The implementation is required to document this.
Question 20: Does the implementation support tasking-safe operations?
Response
Not Applicable
Rationale
An implementation may support tasking-safe operations, and if it does, the blocking behavior of CORBA operations will be managed at the task or program level. The implementation is required to document support and, if support is present, how it is managed.
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
Yes
Rationale
The implementation is required to document this optional behavior.
Copyright © 1998-2011 The Open Group. All Rights Reserved.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.