HomeAbout Us A-Z IndexSearchInquiries RegisterLoginPress Shop
Conformance Statement

Product Standard: CORBA 2.3

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 2.3

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 Language Mappings

Question 1: Which language mappings does the product support?

Response

Rationale

Reference


1.2 Product Profile

Question 2: Which of the following optional parts of the CORBA 2.3 Technical Standard does the product support?

Response

Rationale

Reference


1.3 Policy Domains

Question 3: Is management of Policy Domains supported?

Response

Rationale

Reference


1.4 Pragmas

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

Response

Rationale

Reference


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

Response

Rationale

Reference


1.5 Name Space

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

Response

Rationale

Reference


1.6 Binding of Object Reference

Question 7: What is the effect of invoking get_policy prior to the object reference being bound?

Response

Rationale

Reference


1.7 POA

Question 8: Does the POA support the RETAIN policy?

Response

Rationale

Reference


Question 9: What is the implementation limit for the number of requests received?

Response

Rationale

Reference


Question 10: Does the implementation support both _non_existent and _not_existent in GIOP?

Response

Rationale

Reference


Question 11: Does the implementation support reference counting?

Response

Rationale

Reference


1.8 IDL-to-C++ Translator

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

Response

Rationale

Reference


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

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 ]