ISO/IEC INTERNATIONAL STANDARD

Transcription

1 INTERNATIONAL STANDARD ISO/IEC This is a preview of "ISO/IEC :2012". Click here to purchase the full version from the ANSI store. First edition Information technology Object Management Group Common Object Request Broker Architecture (CORBA) Part 1: Interfaces Technologies de l'information OMG (Object Management Group) CORBA (Common Object Request Broker Architecture) Partie 1: Interfaces Reference number ISO/IEC 2012

2 This is a preview of "ISO/IEC :2012". Click here to purchase the full version from the ANSI store. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel Fax copyright@iso.org Web Published in Switzerland ii ISO/IEC 2012 All rights reserved

3 Table of Contents Foreword...xvii Introduction...xix 1 Scope Conformance and Compliance Normative References Additional Information Outline of Contents Keywords for Requirement Statements The Object Model General Overview Object Semantics Objects Requests Object Creation and Destruction Types Interfaces Value Types Abstract Interfaces Operations Attributes Object Implementation The Execution Model: Performing Services The Construction Model CORBA Overview General ISO/IEC All rights reserved iii

4 6.2 Structure of an Object Request Broker Object Request Broker Clients Object Implementations Object References OMG Interface Definition Language Mapping of IDL to Programming Languages Client Stubs Dynamic Invocation Interface Implementation Skeleton Dynamic Skeleton Interface Object Adapters ORB Interface Interface Repository Implementation Repository Example ORBs Client- and Implementation-resident ORB Server-based ORB System-based ORB Library-based ORB Structure of a Client Structure of an Object Implementation Structure of an Object Adapter CORBA Required Object Adapter Portable Object Adapter The Integration of Foreign Object Systems IDL Syntax and Semantics Overview Lexical Conventions Tokens Comments Identifiers Keywords Literals Preprocessing IDL Grammar iv ISO/IEC All rights reserved

5 7.5 IDL Specification Import Declaration Module Declaration Interface Declaration Interface Header Interface Inheritance Specification Interface Body Forward Declaration Interface Inheritance Abstract Interface Local Interface Value Declaration Regular Value Type Boxed Value Type Abstract Value Type Value Forward Declaration Valuetype Inheritance Constant Declaration Syntax Semantics Type Declaration Basic Types Constructed Types Template Types Complex Declarator Native Types Deprecated Anonymous Types Exception Declaration Operation Declaration Operation Attribute Parameter Declarations Raises Expressions Context Expressions Attribute Declaration Repository Identity Related Declarations Repository Identity Declaration Repository Identifier Prefix Declaration Repository Id Conflict...79 ISO/IEC All rights reserved v

6 7.16 Event Declaration Regular Event Type Abstract Event Type Event Forward Declaration Eventtype Inheritance Component Declaration Component Component Header Component Body Event Sources publishers and emitters Event Sinks Basic and Extended Components Home Declaration Home Home Header Home Body CORBA Module Names and Scoping Qualified Names Scoping Rules and Name Resolution Special Scoping Rules for Type Names ORB Interface Overview The ORB Operations ORB Identity Converting Object References to Strings Getting Service Information Creating a New Context Thread-Related Operations Object Reference Operations Determining the Object Interface Duplicating and Releasing Copies of Object References Nil Object References Equivalence Checking Operation Probing for Object Non-Existence Object Reference Identity Type Coercion Considerations Getting Policy Associated with the Object vi ISO/IEC All rights reserved

7 8.3.9 Overriding Associated Policies on an Object Reference Validating Connection Getting the Domain Managers Associated with the Object Getting Component Associated with the Object Getting the ORB LocalObject Operations ValueBase Operations ORB and OA Initialization and Initial References ORB Initialization Obtaining Initial Object References Configuring Initial Service References Context Object Introduction Context Object Operations Current Object Policy Object Definition of Policy Object Creation of Policy Objects Usages of Policy Objects Policy Associated with the Execution Environment Specification of New Policy Objects Standard Policies Management of Policies Client Side Policy Management Server Side Policy Management Policy Management Interfaces Management of Policy Domains Basic Concepts Domain Management Operations TypeCodes The TypeCode Interface TypeCode Constants Creating TypeCodes Exceptions Definition of Terms System Exceptions Standard System Exception Definitions Standard Minor Exception Codes ISO/IEC All rights reserved vii

8 9 Value Type Semantics Overview Architecture Abstract Values Operations Value Type vs. Interfaces Parameter Passing Substitutability Issues Widening/Narrowing Value Base Type Life Cycle issues Security Considerations Standard Value Box Definitions Language Mappings General Requirements Language Specific Marshaling Language Specific Value Factory Requirements Value Method Implementation Custom Marshaling Implementation of Custom Marshaling Marshaling Streams Access to the Sending Context Run Time Abstract Interface Semantics Overview Semantics of Abstract Interfaces Usage Guidelines Example Security Considerations Passing Values to Trusted Domains Dynamic Invocation Interface Overview Common Data Structures Memory Usage Return Status and Exceptions viii ISO/IEC All rights reserved

9 11.2 Request Operations create_request add_arg invoke delete send poll_response get_response sendp prepare sendc ORB Operations send_multiple_requests get_next_response and poll_next_response Polling Abstract Valuetype Pollable Abstract Valuetype DIIPollable interface PollableSet List Operations create_list add_item free free_memory get_count create_operation_list Dynamic Skeleton Interface Introduction Overview ServerRequestPseudo-Object ExplicitRequest State: ServerRequestPseudo-Object DSI: Language Mapping ServerRequest s Handling of Operation Parameters Registering Dynamic Implementation Routines Dynamic Management of Any Values General Overview ISO/IEC All rights reserved ix

10 13.3 DynAny API Creating a DynAny Object The DynAny Interface The DynFixed Interface The DynEnum Interface The DynStruct Interface The DynUnion Interface The DynSequence Interface The DynArray Interface The DynValueCommon Interface The DynValue Interface The DynValueBox Interface Usage in C++ Language Dynamic Creation of CORBA::Any values Dynamic Interpretation of CORBA::Any values The Interface Repository Overview Scope of an Interface Repository Implementation Dependencies Managing Interface Repositories Basics Names and Identifiers Types and TypeCodes Interface Repository Objects Structure and Navigation of the Interface Repository Interface Repository Interfaces Supporting Type Definitions IRObject Contained Container IDLType Repository ModuleDef ConstantDef TypedefDef StructDef UnionDef EnumDef AliasDef x ISO/IEC All rights reserved

11 PrimitiveDef StringDef WstringDef FixedDef SequenceDef ArrayDef ExceptionDef AttributeDef ExtAttributeDef OperationDef InterfaceDef ExtInterfaceDef AbstractInterfaceDef ExtAbstractInterfaceDef LocalInterfaceDef ExtLocalInterfaceDef ValueMemberDef ValueDef ExtValueDef ValueBoxDef NativeDef Component Interface Repository Interfaces ComponentIR::Container ComponentIR::Repository ComponentIR::ProvidesDef ComponentIR::UsesDef ComponentIR::EventDef ComponentIR::EventPortDef ComponentIR::EmitsDef ComponentIR::PublishesDef ComponentIR::ConsumesDef ComponentIR::ComponentDef ComponentIR::FactoryDef ComponentIR::FinderDef ComponentIR::HomeDef RepositoryIds IDL Format RMI Hashed Format DCE UUID Format LOCAL Format Pragma Directives for RepositoryId For More Information ISO/IEC All rights reserved xi

12 RepositoryIDs for OMG-Specified Types Uniqueness Constraints on Repository IDs IDL for Interface Repository The Portable Object Adapter Overview Abstract Model Description Model Components Model Architecture POA Creation Reference Creation Object Activation States Request Processing Implicit Activation Multi-threading Dynamic Skeleton Interface Location Transparency Interfaces The Servant IDL Type POAManager Interface POAManagerFactory Interface AdapterActivator Interface ServantManager Interface ServantActivator Interface ServantLocator Interface POA Policy Objects POA Interface Current Operations IDL for PortableServer Module UML Description of PortableServer Usage Scenarios Getting the Root POA Creating a POA Explicit Activation with POA-assigned Object Ids Explicit Activation with User-assigned Object Ids Creating References before Activation Servant Manager Definition and Creation Object Activation on Demand Persistent Objects with POA-assigned Ids xii ISO/IEC All rights reserved

13 Multiple Object Ids Mapping to a Single Servant One Servant for All Objects Single Servant, Many Objects and Types, Using DSI Portable Interceptors Introduction Object Creation Client Sends Request Server Receives Request Server Sends Reply Client Receives Reply General Behavior of Local Objects Interceptor Interface Request Interceptors Design Principles General Flow Rules The Flow Stack Visual Model The Request Interceptor Points Client-Side Interceptor Client-Side Interception Points Client-Side Interception Point Flow Server-Side Interceptor Server-Side Interception Points Server-Side Interception Point Flow Request Information RequestInfo Interface ClientRequestInfo Interface ServerRequestInfo Interface ForwardRequest Exception Portable Interceptor Current Overview Obtaining the Portable Interceptor Current Portable Interceptor Current Interface Use of Portable Interceptor Current IOR Interceptor Overview An Abstract Model for Object Adapters Object Reference Template IORInterceptor Interface IORInfo Interface ISO/IEC All rights reserved xiii

14 16.7 Interceptor Policy Objects ProcessingMode Policy PolicyFactory PolicyFactory Interface Registering Interceptors ORBInitializer Interface ORBInitInfo Interface register_orb_initializer Operation Notes about Registering Interceptors Dynamic Initial References register_initial_reference Module Dynamic NVList PIDL Represented by ParameterList IDL ContextList PIDL Represented by ContextList IDL ExceptionList PIDL Represented by ExceptionList IDL Context PIDL Represented by RequestContext IDL Consolidated IDL Dynamic Portions of IOP Relevant to Portable Interceptor PortableInterceptor CORBA Messaging General Quality of Service Messaging Quality of Service Rebind Support Synchronization Scope Request and Reply Priority Request and Reply Timeout Routing Queue Ordering Propagation of Messaging QoS Structures Messaging QoS Profile Component Messaging QoS Service Context Messaging Programming Model Running Example xiv ISO/IEC All rights reserved

15 17.7 Async Operation Mapping Callback Model Signatures (sendc) Polling Model Signatures (sendp) Exception Delivery in the Callback Model Messaging::ExceptionHolder valuetype Type-Specific ReplyHandler Mapping ReplyHandler Operations for NO_EXCEPTION Replies ReplyHandler Operations for Exceptional Replies Example Generic Poller Value operation_target operation_name associated_handler is_from_poller Type-Specific Poller Mapping Basic Type-Specific Poller Persistent Type-Specific Poller Example Example Programmer Usage Example Programmer Usage (Examples Mapped to C++) Client-Side C++ Example for the Asynchronous Method Signatures Client-Side C++ Example of the Callback Model Client-Side C++ Example of the Polling Model Server Side Message Routing Interoperability Routing Object References Message Routing Structures Interfaces Routing Protocol Router Administration Constants Exceptions Valuetypes Interfaces CORBA Messaging IDL Messaging Module MessageRouting Module ISO/IEC All rights reserved xv

16 Chapter 17 Annexes A.1 QoS Abstract Model Design A.2 Model Components A.2.1 Component Relationships A.2.2 Component Design A.3 AMI/TII Abstract Model Design A.3.1 Asynchronous Method Invocation Components A.3.2 Time-Independent Invocation Components A.3.3 Component Relationships A.3.4 Callback Model Detailed Design A.3.5 Poller/PersistentRequest Detailed Design A.4 Message Routing Abstract Model Design A.4.1 Model Components A.4.2 Component Relationships A.4.3 Router Administration Design B.1 Conformance Issues B.2 Compatibility Issues B.2.1 Transaction Service B.2.2 Changes to Current OTS Behavior B.2.3 Security Service Annex A - IDL Tags and Exceptions Annex B - Legal Information xvi ISO/IEC All rights reserved

17 Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/IEC was prepared by Technical Committee ISO/IEC JTC1, Information technology, in collaboration with the Object Management Group (OMG), following the submission and processing as a Publicly Available Specification (PAS) of the OMG Common Object Request Broker Architecture (CORBA) specification Part 1 Version 3.1 CORBA Interfaces. ISO/IEC is related to: ITU-T Recommendation X.902 (1995) ISO/IEC :1996, Information Technology - Open Distributed Processing - Reference Model: Foundations ITU-T Recommendation X.903 (1995) ISO/IEC :1996, Information Technology - Open Distributed Processing - Reference Model: Architecture ITU-T Recommendation X.920 (1997) ISO/IEC 14750:1997, Information Technology - Open Distributed Processing - Interface Definition Language ISO/IEC , Information Technology - Open Distributed Processing - CORBA Specification Part 2: CORBA Interoperability ISO/IEC , Information Technology - Open Distributed Processing - CORBA Specification Part 3: CORBA Components ISO/IEC consists of the following parts, under the general title Information technology - Open distributed processing - CORBA specification: Part 1: CORBA Interfaces Part 2: CORBA Interoperability Part 3: CORBA Components ISO/IEC All rights reserved xvii

18 It is the common core of the CORBA specification. Optional parts of CORBA, such as mappings to particular programming languages, Real-time CORBA extensions, and the minimum CORBA profile for embedded systems are documented in the other specifications that together comprise the complete CORBA specification. Please visit the CORBA download page at to find the complete CORBA specification set. Apart from this Foreword, the text of this International Standard is identical with that for the OMG specification for CORBA, v3.1.1, Part 1. xviii ISO/IEC All rights reserved

19 Introduction The rapid growth of distributed processing has led to a need for a coordinating framework for this standardization and ITU-T Recommendations X ISO/IEC 10746, the Reference Model of Open Distributed Processing (RM-ODP) provides such a framework. It defines an architecture within which support of distribution, interoperability and portability can be integrated. RM-ODP Part 2 (ISO/IEC ) defines the foundational concepts and modeling framework for describing distributed systems. The scopes and objectives of the RM-ODP Part 2 and the UML, while related, are not the same and, in a number of cases, the RM-ODP Part 2 and the UML specification use the same term for concepts which are related but not identical (e.g., interface). Nevertheless, a specification using the Part 2 modeling concepts can be expressed using UML with appropriate extensions (using stereotypes, tags, and constraints). RM-ODP Part 3 (ISO/IEC ) specifies a generic architecture of open distributed systems, expressed using the foundational concepts and framework defined in Part 2. Given the relation between UML as a modeling language and Part 3 of the RM-ODP standard, it is easy to show that UML is suitable as a notation for the individual viewpoint specifications defined by the RM-ODP. This International Standard for CORBA Interfaces is a standard for the technology specification of an ODP system. It defines a technology to provide the infrastructure required to support functional distribution of an ODP system, specifying functions required to manage physical distribution, communications, processing and storage, and the roles of different technology objects in supporting those functions. Context of CORBA The key to understanding the structure of the CORBA architecture is the Reference Model, which consists of the following components: Object Request Broker, which enables objects to transparently make and receive requests and responses in a distributed environment. It is the foundation for building applications from distributed objects and for interoperability between applications in hetero- and homogeneous environments. The architecture and specifications of the Object Request Broker are described in this manual. Object Services, a collection of services (interfaces and objects) that support basic functions for using and implementing objects. Services are necessary to construct any distributed application and are always independent of application domains. For example, the Life Cycle Service defines conventions for creating, deleting, copying, and moving objects; it does not dictate how the objects are implemented in an application. Specifications for Object Services are contained in CORBAservices: Common Object Services Specification. Common Facilities, a collection of services that many applications may share, but which are not as fundamental as the Object Services. For instance, a system management or electronic mail facility could be classified as a common facility. Information about Common Facilities will be contained in CORBAfacilities: Common Facilities Architecture. Application Objects, which are products of a single vendor on in-house development group that controls their interfaces. Application Objects correspond to the traditional notion of applications, so they are not standardized by OMG. Instead, Application Objects constitute the uppermost layer of the Reference Model. ISO/IEC All rights reserved xix

20 The Object Request Broker, then, is the core of the Reference Model. It is like a telephone exchange, providing the basic mechanism for making and receiving calls. Combined with the Object Services, it ensures meaningful communication between CORBA-compliant applications. The architecture and specifications described in this standard are aimed at software designers and developers who want to produce applications that comply with OMG specifications for the Object Request Broker (ORB), or this standard (ISO/ IEC 19500). The benefit of compliance is, in general, to be able to produce interoperable applications that are based on distributed, interoperating objects. The ORB provides the mechanisms by which objects transparently make requests and receive responses. Hence, the ORB provides interoperability between applications on different machines in heterogeneous distributed environments and seamlessly interconnects multiple object systems. This Part of this International Standard includes normative and non-normative annexes. xx ISO/IEC All rights reserved

21 This is a preview of "ISO/IEC :2012". Click here to purchase the full version from the ANSI store. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel Fax copyright@iso.org Web Published in Switzerland ii ISO/IEC 2012 All rights reserved

22 Table of Contents Foreword...xvii Introduction...xix 1 Scope Conformance and Compliance Normative References Additional Information Outline of Contents Keywords for Requirement Statements The Object Model General Overview Object Semantics Objects Requests Object Creation and Destruction Types Interfaces Value Types Abstract Interfaces Operations Attributes Object Implementation The Execution Model: Performing Services The Construction Model CORBA Overview General ISO/IEC All rights reserved iii

23 6.2 Structure of an Object Request Broker Object Request Broker Clients Object Implementations Object References OMG Interface Definition Language Mapping of IDL to Programming Languages Client Stubs Dynamic Invocation Interface Implementation Skeleton Dynamic Skeleton Interface Object Adapters ORB Interface Interface Repository Implementation Repository Example ORBs Client- and Implementation-resident ORB Server-based ORB System-based ORB Library-based ORB Structure of a Client Structure of an Object Implementation Structure of an Object Adapter CORBA Required Object Adapter Portable Object Adapter The Integration of Foreign Object Systems IDL Syntax and Semantics Overview Lexical Conventions Tokens Comments Identifiers Keywords Literals Preprocessing IDL Grammar iv ISO/IEC All rights reserved

24 7.5 IDL Specification Import Declaration Module Declaration Interface Declaration Interface Header Interface Inheritance Specification Interface Body Forward Declaration Interface Inheritance Abstract Interface Local Interface Value Declaration Regular Value Type Boxed Value Type Abstract Value Type Value Forward Declaration Valuetype Inheritance Constant Declaration Syntax Semantics Type Declaration Basic Types Constructed Types Template Types Complex Declarator Native Types Deprecated Anonymous Types Exception Declaration Operation Declaration Operation Attribute Parameter Declarations Raises Expressions Context Expressions Attribute Declaration Repository Identity Related Declarations Repository Identity Declaration Repository Identifier Prefix Declaration Repository Id Conflict...79 ISO/IEC All rights reserved v

25 7.16 Event Declaration Regular Event Type Abstract Event Type Event Forward Declaration Eventtype Inheritance Component Declaration Component Component Header Component Body Event Sources publishers and emitters Event Sinks Basic and Extended Components Home Declaration Home Home Header Home Body CORBA Module Names and Scoping Qualified Names Scoping Rules and Name Resolution Special Scoping Rules for Type Names ORB Interface Overview The ORB Operations ORB Identity Converting Object References to Strings Getting Service Information Creating a New Context Thread-Related Operations Object Reference Operations Determining the Object Interface Duplicating and Releasing Copies of Object References Nil Object References Equivalence Checking Operation Probing for Object Non-Existence Object Reference Identity Type Coercion Considerations Getting Policy Associated with the Object vi ISO/IEC All rights reserved

26 8.3.9 Overriding Associated Policies on an Object Reference Validating Connection Getting the Domain Managers Associated with the Object Getting Component Associated with the Object Getting the ORB LocalObject Operations ValueBase Operations ORB and OA Initialization and Initial References ORB Initialization Obtaining Initial Object References Configuring Initial Service References Context Object Introduction Context Object Operations Current Object Policy Object Definition of Policy Object Creation of Policy Objects Usages of Policy Objects Policy Associated with the Execution Environment Specification of New Policy Objects Standard Policies Management of Policies Client Side Policy Management Server Side Policy Management Policy Management Interfaces Management of Policy Domains Basic Concepts Domain Management Operations TypeCodes The TypeCode Interface TypeCode Constants Creating TypeCodes Exceptions Definition of Terms System Exceptions Standard System Exception Definitions Standard Minor Exception Codes ISO/IEC All rights reserved vii

27 9 Value Type Semantics Overview Architecture Abstract Values Operations Value Type vs. Interfaces Parameter Passing Substitutability Issues Widening/Narrowing Value Base Type Life Cycle issues Security Considerations Standard Value Box Definitions Language Mappings General Requirements Language Specific Marshaling Language Specific Value Factory Requirements Value Method Implementation Custom Marshaling Implementation of Custom Marshaling Marshaling Streams Access to the Sending Context Run Time Abstract Interface Semantics Overview Semantics of Abstract Interfaces Usage Guidelines Example Security Considerations Passing Values to Trusted Domains Dynamic Invocation Interface Overview Common Data Structures Memory Usage Return Status and Exceptions viii ISO/IEC All rights reserved

28 11.2 Request Operations create_request add_arg invoke delete send poll_response get_response sendp prepare sendc ORB Operations send_multiple_requests get_next_response and poll_next_response Polling Abstract Valuetype Pollable Abstract Valuetype DIIPollable interface PollableSet List Operations create_list add_item free free_memory get_count create_operation_list Dynamic Skeleton Interface Introduction Overview ServerRequestPseudo-Object ExplicitRequest State: ServerRequestPseudo-Object DSI: Language Mapping ServerRequest s Handling of Operation Parameters Registering Dynamic Implementation Routines Dynamic Management of Any Values General Overview ISO/IEC All rights reserved ix

29 13.3 DynAny API Creating a DynAny Object The DynAny Interface The DynFixed Interface The DynEnum Interface The DynStruct Interface The DynUnion Interface The DynSequence Interface The DynArray Interface The DynValueCommon Interface The DynValue Interface The DynValueBox Interface Usage in C++ Language Dynamic Creation of CORBA::Any values Dynamic Interpretation of CORBA::Any values The Interface Repository Overview Scope of an Interface Repository Implementation Dependencies Managing Interface Repositories Basics Names and Identifiers Types and TypeCodes Interface Repository Objects Structure and Navigation of the Interface Repository Interface Repository Interfaces Supporting Type Definitions IRObject Contained Container IDLType Repository ModuleDef ConstantDef TypedefDef StructDef UnionDef EnumDef AliasDef x ISO/IEC All rights reserved

30 PrimitiveDef StringDef WstringDef FixedDef SequenceDef ArrayDef ExceptionDef AttributeDef ExtAttributeDef OperationDef InterfaceDef ExtInterfaceDef AbstractInterfaceDef ExtAbstractInterfaceDef LocalInterfaceDef ExtLocalInterfaceDef ValueMemberDef ValueDef ExtValueDef ValueBoxDef NativeDef Component Interface Repository Interfaces ComponentIR::Container ComponentIR::Repository ComponentIR::ProvidesDef ComponentIR::UsesDef ComponentIR::EventDef ComponentIR::EventPortDef ComponentIR::EmitsDef ComponentIR::PublishesDef ComponentIR::ConsumesDef ComponentIR::ComponentDef ComponentIR::FactoryDef ComponentIR::FinderDef ComponentIR::HomeDef RepositoryIds IDL Format RMI Hashed Format DCE UUID Format LOCAL Format Pragma Directives for RepositoryId For More Information ISO/IEC All rights reserved xi

31 RepositoryIDs for OMG-Specified Types Uniqueness Constraints on Repository IDs IDL for Interface Repository The Portable Object Adapter Overview Abstract Model Description Model Components Model Architecture POA Creation Reference Creation Object Activation States Request Processing Implicit Activation Multi-threading Dynamic Skeleton Interface Location Transparency Interfaces The Servant IDL Type POAManager Interface POAManagerFactory Interface AdapterActivator Interface ServantManager Interface ServantActivator Interface ServantLocator Interface POA Policy Objects POA Interface Current Operations IDL for PortableServer Module UML Description of PortableServer Usage Scenarios Getting the Root POA Creating a POA Explicit Activation with POA-assigned Object Ids Explicit Activation with User-assigned Object Ids Creating References before Activation Servant Manager Definition and Creation Object Activation on Demand Persistent Objects with POA-assigned Ids xii ISO/IEC All rights reserved

32 Multiple Object Ids Mapping to a Single Servant One Servant for All Objects Single Servant, Many Objects and Types, Using DSI Portable Interceptors Introduction Object Creation Client Sends Request Server Receives Request Server Sends Reply Client Receives Reply General Behavior of Local Objects Interceptor Interface Request Interceptors Design Principles General Flow Rules The Flow Stack Visual Model The Request Interceptor Points Client-Side Interceptor Client-Side Interception Points Client-Side Interception Point Flow Server-Side Interceptor Server-Side Interception Points Server-Side Interception Point Flow Request Information RequestInfo Interface ClientRequestInfo Interface ServerRequestInfo Interface ForwardRequest Exception Portable Interceptor Current Overview Obtaining the Portable Interceptor Current Portable Interceptor Current Interface Use of Portable Interceptor Current IOR Interceptor Overview An Abstract Model for Object Adapters Object Reference Template IORInterceptor Interface IORInfo Interface ISO/IEC All rights reserved xiii

33 16.7 Interceptor Policy Objects ProcessingMode Policy PolicyFactory PolicyFactory Interface Registering Interceptors ORBInitializer Interface ORBInitInfo Interface register_orb_initializer Operation Notes about Registering Interceptors Dynamic Initial References register_initial_reference Module Dynamic NVList PIDL Represented by ParameterList IDL ContextList PIDL Represented by ContextList IDL ExceptionList PIDL Represented by ExceptionList IDL Context PIDL Represented by RequestContext IDL Consolidated IDL Dynamic Portions of IOP Relevant to Portable Interceptor PortableInterceptor CORBA Messaging General Quality of Service Messaging Quality of Service Rebind Support Synchronization Scope Request and Reply Priority Request and Reply Timeout Routing Queue Ordering Propagation of Messaging QoS Structures Messaging QoS Profile Component Messaging QoS Service Context Messaging Programming Model Running Example xiv ISO/IEC All rights reserved

34 17.7 Async Operation Mapping Callback Model Signatures (sendc) Polling Model Signatures (sendp) Exception Delivery in the Callback Model Messaging::ExceptionHolder valuetype Type-Specific ReplyHandler Mapping ReplyHandler Operations for NO_EXCEPTION Replies ReplyHandler Operations for Exceptional Replies Example Generic Poller Value operation_target operation_name associated_handler is_from_poller Type-Specific Poller Mapping Basic Type-Specific Poller Persistent Type-Specific Poller Example Example Programmer Usage Example Programmer Usage (Examples Mapped to C++) Client-Side C++ Example for the Asynchronous Method Signatures Client-Side C++ Example of the Callback Model Client-Side C++ Example of the Polling Model Server Side Message Routing Interoperability Routing Object References Message Routing Structures Interfaces Routing Protocol Router Administration Constants Exceptions Valuetypes Interfaces CORBA Messaging IDL Messaging Module MessageRouting Module ISO/IEC All rights reserved xv

35 Chapter 17 Annexes A.1 QoS Abstract Model Design A.2 Model Components A.2.1 Component Relationships A.2.2 Component Design A.3 AMI/TII Abstract Model Design A.3.1 Asynchronous Method Invocation Components A.3.2 Time-Independent Invocation Components A.3.3 Component Relationships A.3.4 Callback Model Detailed Design A.3.5 Poller/PersistentRequest Detailed Design A.4 Message Routing Abstract Model Design A.4.1 Model Components A.4.2 Component Relationships A.4.3 Router Administration Design B.1 Conformance Issues B.2 Compatibility Issues B.2.1 Transaction Service B.2.2 Changes to Current OTS Behavior B.2.3 Security Service Annex A - IDL Tags and Exceptions Annex B - Legal Information xvi ISO/IEC All rights reserved

36 Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/IEC was prepared by Technical Committee ISO/IEC JTC1, Information technology, in collaboration with the Object Management Group (OMG), following the submission and processing as a Publicly Available Specification (PAS) of the OMG Common Object Request Broker Architecture (CORBA) specification Part 1 Version 3.1 CORBA Interfaces. ISO/IEC is related to: ITU-T Recommendation X.902 (1995) ISO/IEC :1996, Information Technology - Open Distributed Processing - Reference Model: Foundations ITU-T Recommendation X.903 (1995) ISO/IEC :1996, Information Technology - Open Distributed Processing - Reference Model: Architecture ITU-T Recommendation X.920 (1997) ISO/IEC 14750:1997, Information Technology - Open Distributed Processing - Interface Definition Language ISO/IEC , Information Technology - Open Distributed Processing - CORBA Specification Part 2: CORBA Interoperability ISO/IEC , Information Technology - Open Distributed Processing - CORBA Specification Part 3: CORBA Components ISO/IEC consists of the following parts, under the general title Information technology - Open distributed processing - CORBA specification: Part 1: CORBA Interfaces Part 2: CORBA Interoperability Part 3: CORBA Components ISO/IEC All rights reserved xvii

37 It is the common core of the CORBA specification. Optional parts of CORBA, such as mappings to particular programming languages, Real-time CORBA extensions, and the minimum CORBA profile for embedded systems are documented in the other specifications that together comprise the complete CORBA specification. Please visit the CORBA download page at to find the complete CORBA specification set. Apart from this Foreword, the text of this International Standard is identical with that for the OMG specification for CORBA, v3.1.1, Part 1. xviii ISO/IEC All rights reserved

38 Introduction The rapid growth of distributed processing has led to a need for a coordinating framework for this standardization and ITU-T Recommendations X ISO/IEC 10746, the Reference Model of Open Distributed Processing (RM-ODP) provides such a framework. It defines an architecture within which support of distribution, interoperability and portability can be integrated. RM-ODP Part 2 (ISO/IEC ) defines the foundational concepts and modeling framework for describing distributed systems. The scopes and objectives of the RM-ODP Part 2 and the UML, while related, are not the same and, in a number of cases, the RM-ODP Part 2 and the UML specification use the same term for concepts which are related but not identical (e.g., interface). Nevertheless, a specification using the Part 2 modeling concepts can be expressed using UML with appropriate extensions (using stereotypes, tags, and constraints). RM-ODP Part 3 (ISO/IEC ) specifies a generic architecture of open distributed systems, expressed using the foundational concepts and framework defined in Part 2. Given the relation between UML as a modeling language and Part 3 of the RM-ODP standard, it is easy to show that UML is suitable as a notation for the individual viewpoint specifications defined by the RM-ODP. This International Standard for CORBA Interfaces is a standard for the technology specification of an ODP system. It defines a technology to provide the infrastructure required to support functional distribution of an ODP system, specifying functions required to manage physical distribution, communications, processing and storage, and the roles of different technology objects in supporting those functions. Context of CORBA The key to understanding the structure of the CORBA architecture is the Reference Model, which consists of the following components: Object Request Broker, which enables objects to transparently make and receive requests and responses in a distributed environment. It is the foundation for building applications from distributed objects and for interoperability between applications in hetero- and homogeneous environments. The architecture and specifications of the Object Request Broker are described in this manual. Object Services, a collection of services (interfaces and objects) that support basic functions for using and implementing objects. Services are necessary to construct any distributed application and are always independent of application domains. For example, the Life Cycle Service defines conventions for creating, deleting, copying, and moving objects; it does not dictate how the objects are implemented in an application. Specifications for Object Services are contained in CORBAservices: Common Object Services Specification. Common Facilities, a collection of services that many applications may share, but which are not as fundamental as the Object Services. For instance, a system management or electronic mail facility could be classified as a common facility. Information about Common Facilities will be contained in CORBAfacilities: Common Facilities Architecture. Application Objects, which are products of a single vendor on in-house development group that controls their interfaces. Application Objects correspond to the traditional notion of applications, so they are not standardized by OMG. Instead, Application Objects constitute the uppermost layer of the Reference Model. ISO/IEC All rights reserved xix