Common Object Request Broker Architecture (CORBA) V2.3
|Document Number: X01OB|
©June 2001, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.
Copyright © November 1999, Object Management Group, Inc.
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.
CORBA® is a registered trademark, and ORBTM;, IIOPTM;, and OMG Interface Definition Language (IDL)TM; are trademarks of the Object Management Group, Inc. in the United States.
Common Object Request Broker Architecture (CORBA) V2.3
The Object Management Group has developed an architecture and specification for object technology use, management, interworking (the exchange of data between object models), and interoperability (the means of message exchange between object request brokers). Products which are developed in compliance with this architecture and specification include an Object Request Broker (ORB) which enables objects to transparently make and receive requests and responses in a distributed environment. In addition to the ORB, products may also supply object services that applications may share. These object services are a collection of services (interfaces and objects) that support basic functions for using and implementing objects, as well as common facilities.
Products that conform to this Product Standard shall include an implementation of the OMG abstract object model that contains the following:
The Technical Standard specifying the functionality in CORBA V2.3-compliant products, including specification of the CORBA V2.3 architecture and components, is found in The Common Object Request Broker: Architecture and Specification, Revision 2.3.11 and the associated Language Mapping Specifications. Hereinafter, these documents are referred to as "the Specification".
In addition to the core ORB technology, conforming products provide an implementation of the ORB interoperability architecture that supplies the framework for ORB interoperability, including the General Inter-ORB Protocol (GIOP) and the Internet Inter-ORB Protocol (IIOP). Products described by this Product Standard correspond to Interoperability-compliant ORBs, as defined by Section 12.3.4 of the Specification.
Each implementation must include one or both of the following language mappings of OMG IDL, which are aligned with CORBA V2.3:
This Product Standard does not require inclusion of the following components of the Specification:
A conformant product consists of a particular combination of software supported on certain specified hardware platforms, and the specific implementation of the product to be registered must therefore be uniquely identified.
A single configuration of the product shall meet all mandatory conformance requirements. In addition, products may implement optional facilities.
Conformant products may also provide additional standards-based or proprietary services, as long as the mandatory conformance requirements continue to be met, or the vendor provides instructions on how the user may configure the environment such that the product meets the conformance requirements.
A single configuration of the product shall meet all the conformance
requirements defined in the indicated chapter of the Specification as
noted below. It shall support all the definitions of those chapters
including all functions and headers, all protocol messages, all
externally stored or transmitted data formats, and all
application/service capabilities, unless otherwise noted below.
OMG Interface Definition Language (IDL) (Chapter 3 of the Specification) and one or both of the C++ and Java language mappings contained in the associated Language Mapping documents of the Specification, with the following exception:
GIOP and IIOP (Chapters 12, 13, 14, and 15 of the Specification)
The IIOP services in a conformant product require reliable, end-to-end connections for their execution. Consequently, they are defined to be implemented on top of the Transmission Control Protocol (TCP). TCP defines a method for connection-oriented, end-to-end communications to take place over Internet Protocol-based networks.
Products conformant to this Product Standard, and the respective environments in which their conformance has been established, shall conform to the following:
For a conformant product which includes the C++ Language mapping, a C++ compiler that supports all the features described in ISO/IEC 14882:19982 is required to be supported. Further, the C++ compiler must support templates and must supply native exception handling. Namespace and RTTI support are not required.
For a conformant product which includes the Java Language mapping, a Java compiler that supports all the features described in the Java Platform Core API,3 JDK Level 1.1 or higher, is required to be supported.
There are no dependencies on Operating System interfaces.
The Object Management Group's The Common Object Request Broker: Architecture and Specification and the associated Language Mapping Specifications, as described in the DESCRIPTION.
A Test Report from the currently authorized release of the VSOrb (for C++ implementations) or the VSJOrb (for Java implementations) Test Suite. Refer to www.opengroup.org/testing to ascertain the currently authorized version of the test suites, and to Testing and the Open Brand for detailed testing requirements.
The release of VSOrb and VSJOrb contains test coverage in the following areas:
For products which offer a C++ Language binding, the IIOP tests must run successfully in a multi-system, multi-vendor conformant ORB product configuration.
For products which offer a Java Language binding, the IIOP tests must run successfully in a multi-system, multi-vendor conformant ORB product configuration.
Any comments relating to the material contained in this document may be submitted to The Open Group at:
The Open Groupor by electronic mail to:
Berkshire, RG1 1AX