HomeAbout Us A-Z IndexSearchInquiries RegisterLoginPress Shop
Conformance Statement

Product Standard: CORBA

This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

Organization
Author


1. CORBA

Product Information

Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements.

Product IdentificationVersion/Release NumberProduct Supplier
 
 
 
 
 

Environment Specification

Please note that unlike with Operating Systems it is the test environment not the binary compatible family that drives the branding here. In fact, binary compatible family has little meaning in this context.

Product registration applies to software products operating in a specific hardware or hardware/software environment.

A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

Testing Environment Binary-compatible Family Portability Environment Indicator of Compliance Compliance Details
None. Test Suite:
Test Report:
None. Test Suite:
Test Report:
None. Test Suite:
Test Report:
None. Test Suite:
Test Report:
None. Test Suite:
Test Report:

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

Waiver NumberExpiry Date


1.1 CORBA Core

1.1.1 OMG IDL Syntax and Semantics

Question 1: Does the product interpret or ignore pragmas for RepositoryID formats?

Response

Rationale

Reference


Question 2: Does the product require interface-specific pragmas to precede an Interface body?

Response

Rationale

Reference


Question 3: Does the product require interface-specific pragmas to precede an operation declaration?

Response

Rationale

Reference


1.1.2 Object Adapters

Question 4: Which object adapters does the product supply?

Response

Rationale

Reference


1.1.3 DII Routines

Question 5: Do DII routines return a status code?

Response

Rationale

Reference


1.1.4 Name Space Partitioning

Question 6: Does the product use the period character to partition the name space?

Response

Rationale

Reference


1.1.5 Interface Repository

Question 7: Does this implementation support the Interface Repository?

Response

Rationale

Reference


1.2 Language Mappings

Question 8: Which language mappings does the product support?

Response

Rationale

Reference


1.3 C++ Mapping

Question 9: Can the implementation take advantage of templates if they are supported by the target environment?

Response

Rationale

Reference


Question 10: Can the implementation's IDL-to-C++ translator support 64-bit integer types?

Response

Rationale

Reference


Question 11: For which target environment can the implementation's IDL-to-C++ translator provide a mapping for module?

Response

Rationale

Reference


Question 12: For which exception handling environments can the implementation's IDL-to-C++ translator provide a mapping?

Response

Rationale

Reference


1.4 Smalltalk Mapping

Question 13: How does the product map the IDL interface construct?

Response

Rationale

Reference


Question 14: For which IDL types other than union does the product provide an explicit mapping?

Response

Rationale

Reference


1.5 COBOL Mapping

Question 15: Which constant handling environments can the implementation's IDL-to-COBOL translator support?

Response

Rationale

Reference


Question 16: Which COBOL environments can the implementation's IDL-to-COBOL translator support for mapping basic data types?

Response

Rationale

Reference


1.6 Ada Mapping

Question 17: What additional rules does the product provide for resolving name space clashes?

Response

Rationale

Reference


Question 18: Does the implementation use strings associated with Exception_Message and Exception_Information in the package Ada.Exceptions to ``carry'' exception members?

Response

Rationale

Reference


Question 19: Is access to CORBA services tasking-safe?

Response

Rationale

Reference


Question 20: Does the implementation support tasking-safe operations?

Response

Rationale

Reference


1.7 Interoperability

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

Rationale

Reference


 Copyright © 1998-2002 The Open Group. All Rights Reserved.

 OSF/1, Motif, UNIX, and the "X" device are registered trademarks in the U.S. and other countries, and IT DialTone and The Open Group are trademarks of The Open Group.


[ Home ] [ Testing Home ] [ Conformance Statement Library Home ] [ Search Conformance Statements ] [ Send Feedback ]