OMG CORBA 3.3 — Spec Coverage (WP CORBA Coexistence)

Source: OMG CORBA 3.3 — three volumes as formal documents: * Part 1 (Interfaces, 532 pp.) — formal/12-11-12 * Part 2 (Interoperability, 249 pp.) — formal/12-11-14 * Part 3 (Component Model, 380 pp.) — formal/12-11-16

Context. With the DDS core and the codegen in crates/lang-rules/ and crates/corba-codegen/, ZeroDDS fully covers the DDS PSM. For migrating legacy CORBA applications in the finance industry, ZeroDDS should be able to appear as a drop-in backend: an existing CORBA client compiles and links against Annex-A.1 stubs, runs against ZeroDDS endpoints that speak GIOP/IIOP wire, and can be migrated incrementally to pure DDS without ad-hoc infrastructure swaps.

CORBA coexistence is spread across several implementation crates:

crates/idl-parse/ · docs.rs — IDL grammar (Part 1 §7 IDL syntax)
crates/corba-codegen/ · docs.rs — Annex-A.1 codegen (stubs/skeletons, Part 1 §7)
crates/corba-ir/ · docs.rs — Interface Repository (Part 1 §14)
crates/corba-poa/ · docs.rs — Portable Object Adapter (Part 1 §15)
crates/corba-giop/ · docs.rs — GIOP wire protocol (Part 2 §9)
crates/corba-iiop/ · docs.rs — IIOP transport (Part 2 §9.7)
crates/corba-ior/ · docs.rs — IOR encoding (Part 2 §9.4 / §10.5)
crates/corba-csiv2/ · docs.rs — CSIv2 security (Part 2 §10)
crates/corba-ccm/ · docs.rs — Component Model (Part 3 §6-§9)
crates/corba-ccm-lib/ · docs.rs — CCM container (Part 3 §10)
crates/corba-ccm-ejb/ · docs.rs — EJB integration (Part 3 §11)
crates/corba-dnc/ · docs.rs — Deployment & Configuration (Part 3 §15-§17)
crates/corba-dds-bridge/ · docs.rs — ZeroDDS bridge (no OMG item)
crates/corba-cosnaming/ · docs.rs — COS Naming v1.3 (separate spec)
crates/corba-cos-event/ · docs.rs — COS Event Service v1.2 (separate spec)
crates/dcps/ · docs.rs — DDS PSM core (DDS migration target)
crates/rpc/ · docs.rs — DDS-RPC core (DDS migration target)

CosNaming and CosEventService are standalone OMG specs (formal/04-10-03 and formal/04-10-02); CosEvent has its own spec-coverage file (cos-event-service-1.4.md). CosNaming coverage is carried inline here, because CORBA Part 1 §8.5.2 requires it as a standard initial reference.

Part 1: Interfaces

§1 Scope

Spec: Part 1 §1, p. 1 — scope of the CORBA specification.

Repo: —

Tests: —

Status: n/a (informative) — scope.

§2 Conformance and Compliance

Spec: Part 1 §2.1, p. 1 — “The minimum required for a CORBA-compliant system is adherence to the specifications in this standard and one mapping. Each additional language mapping is a separate, optional compliance point.”

Repo: —

Tests: —

Status: open — adherence to the standard is the sum of the items in this document; evidence of an OMG language mapping is missing. ZeroDDS maps CORBA IDL to Rust (zerodds-corba-rust-1.1, own spec, no OMG mapping); crates/corba-codegen produces stub and skeleton nodes for C++ and Java, without a coverage document against the OMG mappings for C++ or Java.

§3 Normative References

Spec: Part 1 §3, p. 1 — list of normative references.

Repo: —

Tests: —

Status: n/a (informative) — reference list.

§4 Additional Information

Spec: Part 1 §4, p. 2 — outline + keyword conventions (MUST/SHALL/SHOULD/MAY).

Repo: —

Tests: —

Status: n/a (informative) — outline of Part 1 and the reading of the keywords per RFC 2119; no requirement on an implementation.

§5 The Object Model

Spec: Part 1 §5, p. 3 — abstract object model (Objects, Requests, Types, Interfaces, Value Types, Operations, Attributes).

Repo: —

Tests: —

Status: n/a (informative) — conceptual framework, no wire/ code obligation.

§6 CORBA Overview

Spec: Part 1 §6, p. 11 — architecture overview (ORB, stubs, DSI, Object Adapter, IR).

Repo: —

Tests: —

Status: n/a (informative) — overview; the requirements on ORB, DII, DSI, object adapter and IR are in §7–§18.

§7 IDL Syntax and Semantics

Spec: Part 1 §7, p. 27 — complete IDL grammar (lexer, module, interface, value, constant, type, exception, operation, attribute, repository identity, event, component, home, names & scoping).

Repo: crates/idl-cst/src/lex.rs, crates/idl-parse/src/decl.rs, crates/idl-lower/src/lower.rs, crates/corba-codegen/src/repository_id.rs, crates/corba-codegen/src/special_types.rs, crates/corba-codegen/src/skeleton.rs, crates/corba-codegen/src/stub.rs.

Tests: crates/idl-parse/tests/parse.rs::{each_declaration_form_is_recognised, a_file_using_most_of_the_grammar_parses_cleanly_and_round_trips}, crates/idl-lower/tests/conformance.rs::{every_fixture_parses_with_no_diagnostics_beyond_the_extensions_it_declares, every_fixture_lowers_to_exactly_the_diagnostics_it_should}, crates/corba-codegen/src/repository_id.rs::{a_nested_module_path, splitting_takes_the_last_colon_and_checks_the_version_is_a_version}.

Status: done — IDL 4.2 is a superset of CORBA-IDL §7. Rule-by-rule coverage in docs/spec-coverage/idl-4.2.md (649 done / 4 partial). Repository identity (§7.15) is implemented via corba-codegen::repository_id. Component and home declarations (§7.17/§7.18) are restated in Part 3 §6 and are done there.

§8 ORB Interface

Spec: Part 1 §8, p. 93 — ORB pseudo-object: ORB_init, string_to_object/object_to_string, resolve_initial_references, policy management, TypeCodes, standard exceptions.

Repo: crates/corba-ior/src/stringified.rs (string↔︎IOR), crates/corba-ior/src/url.rs (corbaloc/corbaname), crates/corba-poa/src/policies.rs (policy set for POA scope), crates/corba-ir/src/type_code.rs (TypeCode representation), crates/corba-giop/src/error.rs + crates/corba-poa/src/error.rs (standard exceptions as Rust Result).

Tests: crates/corba-ior/src/stringified.rs::tests: round_trip_be, round_trip_le, upper_and_lower_hex_both_decoded, missing_prefix_is_diagnostic, odd_hex_length_is_diagnostic, non_hex_char_is_diagnostic, nil_ior_round_trip; crates/corba-ior/src/url.rs::tests: parse_simple_iiop_corbaloc, default_port_2809_when_missing, rir_endpoint, multi_endpoint_failover, corbaname_with_fragment; crates/corba-ir/src/type_code.rs::tests: well_known_tc_kind_values_match_spec, primitive_tc_has_no_body, struct_tc_carries_id_and_members, sequence_tc_holds_element, enum_tc_holds_member_names.

Status: done — string-↔︎-IOR and URL schemes (§8.2.2, §8.5.2) covered; ORB singleton lifecycle (Orb::init/shutdown/destroy), threading operations (ThreadingMode::SingleThreaded/ThreadPerRequest/ ThreadPool), policy domain manager (Orb::set_policy/get_policy) in crates/corba-ccm/src/orb_core.rs. Standard exceptions as a Rust Result layer.

§9 Value Type Semantics

Spec: Part 1 §9, p. 155 — valuetype marshaling (CDR representation, boxed value, custom marshaling, sending-context runtime).

Repo: crates/wire/src/writer.rs + crates/wire/src/reader.rs (codec base), crates/idl-parse/src/decl.rs (parse_valuetype, value box and custom valuetype), crates/lang-rules/src/coverage.rs (valuetype rule per target language), no dedicated custom-marshal hook in the codegen.

Tests: crates/idl-lower/tests/lowering.rs::{the_other_valuetype_forms_are_unaffected_by_the_box, an_abstract_valuetype_parses_as_a_valuetype, a_forward_declared_valuetype_is_completed_by_its_definition}, crates/corba-codegen/tests/orb_agreement.rs::the_valuebase_holder_is_the_omgs_and_jacorbs_names_a_class_that_does_not_exist, crates/corba-codegen/tests/annex_a1_traits.rs::{table_a8_reads_abstract_and_truncatable_off_the_declaration, table_a9_gives_a_valuebox_its_boxed_trait, every_traited_type_renders_in_every_column}.

Status: done — valuetype IDL parses, lowers and carries an emission rule per target language in lang-rules; a valuetype and a valuebox carry the members Annex A.1.1 gives them in all four PSM columns. Custom-marshal streams via crates/corba-ccm/src/orb_core.rs::StreamableValue trait (marshal/unmarshal/repository_id); sending-context runtime via SendingContext with code_set + truncation_codebase.

§10 Abstract Interface Semantics

Spec: Part 1 §10, p. 171 — abstract interface, marshalling as Object or ValueType.

Repo: crates/idl-parse/src/decl.rs (abstract belongs to two productions — the interface header (79) and <value_abs_def> (127); the fork is in parse_definition), codegen corpus row in crates/corba-codegen/tests/orb-corpus/rows/03-abstractbase.idl.

Tests: crates/idl-lower/tests/lowering.rs::abstract_still_reaches_the_interface_header_it_also_belongs_to, crates/idl-lower/tests/interface_as_type.rs::an_interface_used_as_a_type_resolves_in_every_spelling (the “an abstract interface” row).

Status: done — the parser accepts abstract interface, lowering carries it as its own interface kind, and the codegen corpus holds the row.

§11 Dynamic Invocation Interface (DII)

Spec: Part 1 §11, p. 175 — Request/NVList/NamedValue API for dynamic method calls without a compiled stub.

Repo: crates/corba-ccm/src/dynamic_api.rs::{Request, NvList, NamedValue, ArgFlag} with add_in_arg/add_out_arg operations, ArgFlag::{In, Out, InOut} (spec §11.1.2 wire values 1/2/3) and NVList add_value/count (spec §11.1.3).

Tests: dynamic_api::tests::{arg_flag_round_trip, arg_flag_unknown_value_rejected, nvlist_add_value_increments_count, dii_request_add_in_arg, dii_request_add_out_arg, dii_encode_giop_request_concatenates_input_args, dii_encode_giop_request_inout_treated_as_input, dii_encode_giop_request_round_trip_via_giop_codec}.

Status: done — data model + wire-up: Request::encode_giop_request(request_id, object_key) delivers a corba_giop::Request frame with concatenated In/InOut args; roundtrip via corba_giop::encode_message + decode_message is tested. Spec §11.2 + §15.4.2.

§12 Dynamic Skeleton Interface (DSI)

Spec: Part 1 §12, p. 191 — ServerRequest pseudo-object for generic server implementations.

Repo: crates/corba-ccm/src/dynamic_api.rs::ServerRequest with set_result(value)/set_exception(id, value) operations.

Tests: dynamic_api::tests::{dsi_server_request_set_result, dsi_server_request_set_exception, dsi_input_body_concatenates_in_and_inout, dsi_servant_default_dispatch_via_input_body}.

Status: done — ServerRequest data model + DsiServant trait (spec §12) as a generic server-side dispatch path. Because of layer separation (corba-ccm Layer 8.3 / corba-poa Layer 8.16), the trait is defined orthogonally to corba-poa::Servant and can be implemented in addition. ServerRequest::input_body() concatenates In/InOut args into a flat body; a mock servant in the tests shows the echo roundtrip.

§13 Dynamic Management of Any Values (DynAny)

Spec: Part 1 §13, p. 195 — DynAny API to iterate over any contents without TypeCode-specific codegen.

Repo: crates/corba-ccm/src/dynamic_api.rs::{DynAny, DynAnyKind} with equal/from_any/to_any operations + type-discriminator enum (spec §13.1: Primitive/Struct/Union/Enum/Sequence/Array/Fixed/ Value/ValueBox).

Tests: dynamic_api::tests::{dyn_any_round_trip, dyn_any_equal_same_value, dyn_any_not_equal_different_kind, dyn_any_from_any_round_trip, dyn_any_kind_variants_are_distinct, dyn_any_from_type_code_long_round_trip, dyn_any_from_type_code_long_rejects_truncated_buffer, dyn_any_from_type_code_sequence_preserves_bytes, dyn_any_from_type_code_struct_preserves_bytes_and_id}.

Status: done — DynAny data model + wire-up from_type_code(tc, raw) walks a corba_ir::TypeCode over CDR any bytes; primitive types (Long/ULong/Short/Boolean/String/…) are validated via zerodds_wire::Reader (decode errors are propagated), complex types (Struct/Sequence/Array) preserve the raw bytes plus repository ID. to_cdr() projects the DynAny back.

§14 The Interface Repository

Spec: Part 1 §14, p. 219 — IR as a CORBA service with Container/ Contained/IDLType interface hierarchy; repository IDs; component-IR extensions (Part 3); IDL of the IR.

Repo: crates/corba-ir/src/repository.rs (Repository, Container hierarchy), crates/corba-ir/src/repository_id.rs (IDL/local-format repository IDs), crates/corba-ir/src/type_code.rs (TypeCode backend), crates/corba-ir/src/definition_kind.rs (DK_*).

Tests: crates/corba-ir/src/repository.rs::tests (11 tests): scoped_lookup_descends_hierarchy, absolute_name_builds_scoped_path, operation_def_carries_typed_signature, interface_def_details, register_and_lookup_id, duplicate_id_yields_error, lookup_name_at_top_level, nested_module_lookup_name_recurses, describe_contents_filters_by_kind, definition_carries_type_code, remove_deletes_definition; crates/corba-ir/src/definition_kind.rs::tests::well_known_definition_kinds_match_spec, ::at_least_26_kinds_modeled; crates/corba-ir/src/repository_id.rs::tests::round_trip_omg_namingcontext, ::missing_idl_prefix_is_invalid, ::missing_version_is_invalid.

Status: done — IR interface hierarchy + RepositoryIds + TypeCodes implemented. Component-IR extensions see Part 3 §12 (CCM metamodel).

§15 The Portable Object Adapter (POA)

Spec: Part 1 §15, p. 301 — POA architecture: policies (Lifespan, IdAssignment, IdUniqueness, ServantRetention, RequestProcessing, ImplicitActivation, Thread), object activation, servant manager, adapter activator, POA hierarchy, IDL for PortableServer.

Repo: crates/corba-poa/src/poa.rs (hierarchy + dispatch), crates/corba-poa/src/policies.rs (all 7 standard policies), crates/corba-poa/src/active_object_map.rs (AOM), crates/corba-poa/src/servant.rs + crates/corba-poa/src/servant_manager.rs, crates/corba-poa/src/object_id.rs, crates/corba-poa/src/poa_manager.rs (activation lifecycle).

Tests: crates/corba-poa/src/poa.rs::tests (12 tests): poa_hierarchy_create_find_destroy, default_root_dispatch_via_aom, user_id_activation_with_explicit_oid, use_default_servant_falls_back_to_default, use_servant_manager_with_activator_caches_in_aom, non_retain_with_locator_calls_pre_post_per_invocation, dispatch_in_holding_state_is_rejected, dispatch_in_inactive_state_yields_adapter_inactive, dispatch_in_discarding_state_returns_obj_adapter, invalid_policy_combination_is_rejected_at_construction; crates/corba-poa/src/active_object_map.rs::tests (6), crates/corba-poa/src/policies.rs::tests (8), crates/corba-poa/src/poa_manager.rs::tests::full_state_cycle, crates/corba-poa/src/object_id.rs::tests::system_id_is_8_bytes_big_endian, crates/corba-poa/src/servant.rs::tests::is_a_checks_repository_ids, crates/corba-poa/src/servant_manager.rs::tests::locator_preinvoke_returns_servant_and_cookie.

Status: done — all 7 standard policies + servant-manager path + AOM + POA hierarchy + dispatch implemented. Adapter activator (§15.3.6) covered as a ServantManager variant; if strict separation is required, that would be a small refactor (≤0.5 PW).

§16 Portable Interceptors

Spec: Part 1 §16, p. 357 — client/server request interceptor API, PolicyFactory registration, IORInterceptor (TaggedComponent inject), PI initial reference (PICurrent).

Repo: crates/corba-ccm/src/orb_extensions.rs::{ClientRequestInterceptor, ServerRequestInterceptor, IorInterceptor, InterceptorRegistry, PolicyFactory, PiCurrent, ClientInterceptionPoint, ServerInterceptionPoint} with all 5 client points (send_request/send_poll/receive_reply/receive_exception/ receive_other) + 5 server points (receive_request_service_contexts/ receive_request/send_reply/send_exception/send_other) + registry + PiCurrent slot storage. Pipeline walks (walk_client, walk_server, walk_ior) are wired in crates/corba-iiop/src/connection.rs:: Connection::with_interceptors: read_message/ write_message automatically walk SendRequest/ReceiveReply (client) resp. ReceiveRequest/SendReply (server) when a registry is installed.

Tests: orb_extensions::tests::{registry_add_increments_counts, picurrent_set_get_slot, client_interception_points_distinct, server_interception_points_distinct, registry_walk_client_invokes_all_client_interceptors, registry_walk_ior_collects_tags} + crates/corba-iiop/src/connection.rs::{pipeline_walks_client_send_request, pipeline_walks_server_receive_request, ior_interceptor_fires_on_walk_ior}.

Status: done — PI data model + pipeline integration in the IIOP connection send/receive path.

§17 CORBA Messaging

Spec: Part 1 §17, p. 415 — asynchronous messaging (AMI), time- independent invocations (TII), QoS policies (RebindPolicy, SyncScopePolicy etc.).

Repo: crates/corba-ccm/src/orb_extensions.rs::{MessagingPolicy, AmiReplyHandler, AmiReplySink, dispatch_async_reply, PersistentRequestStore, PersistentRequestEntry} with all 10 policy types (Rebind/SyncScope/RequestPriority/ReplyPriority/Routing/ MaxHops/RequestTime/ReplyTime/RelativeRoundtripTimeout/ RoutingTypeRange) + wire mapping policy_type() -> u32 to OMG Messaging.idl (formal/2011-11-02 §B.5.1). AMI reply dispatch (dispatch_async_reply) maps a corba_giop::Reply onto the three spec callbacks handle_reply / handle_excep / handle_other. TII (time-independent invocations) delivers PersistentRequestStore with add / poll / timeout_expired.

Tests: orb_extensions::tests::{messaging_policies_distinct, ami_reply_handler_distinct, messaging_policy_wire_values_match_omg_messaging_idl, ami_handler_handles_no_exception_reply, ami_handler_handles_user_exception_reply, persistent_request_store_add_poll_timeout}.

Status: done — AMI reply-dispatch bridge onto corba_giop::Reply + TII persistent request store + wire mapping of all 10 messaging policies.

§18 Compression

Spec: Part 1 §18, p. 491 — generic compression framework for GIOP payloads (codec registration, negotiation).

Repo: crates/corba-ccm/src/orb_extensions.rs::{CompressionAlgorithm, ZiopConfig} with None/Zlib/Gzip/Lzma/Deflate algorithms + ZiopConfig (algorithm/min_size_threshold/level).

Tests: orb_extensions::tests::{compression_algorithm_round_trip, compression_algorithm_unknown_rejected, ziop_config_default_no_compression, compression_none_passes_through, compression_zlib_round_trip, compression_gzip_round_trip, compression_deflate_round_trip, compression_lzma_returns_unsupported, compression_zlib_handles_large_block}.

Status: done — compression framework + production codec via flate2 (pure-Rust backend): CompressionAlgorithm::compress(input) and decompress(input) cover None (passthrough), Zlib (RFC 1950), Gzip (RFC 1952), Deflate (RFC 1951). Lzma delivers CompressionError::Unsupported with a decision record (xz2/liblzma build risk disproportionate). A 10 kB block test demonstrates the roundtrip behavior.

Part 2: Interoperability

§1, §3–§5 Scope/References/Terms/Symbols

Spec: Part 2 §1, §3–§5, pp. 1-6 — scope, normative references, term definitions, symbols.

Repo: —

Tests: —

Status: n/a (informative) — scope, reference lists and terms.

§2 Conformance and Compliance — interoperability

Spec: Part 2 §2, p. 1 — “An ORB is considered to be interoperability-compliant when it meets the following requirements”: the APIs for request-level bridges (Dynamic Invocation Interface, Dynamic Skeleton Interface, the object identity operations) and IIOP (GIOP transfer syntax and message formats over TCP/IP). ZIOP is an optional compliance point (item §12).

Repo: crates/corba-ccm/src/dynamic_api.rs (DII, DSI), crates/corba-giop/src/object_ops.rs (_is_a, _non_existent, _interface, _repository_id, _domain_managers, _component), crates/corba-iiop/ (IIOP).

Tests: crates/corba-ccm/src/dynamic_api.rs::tests::dii_encode_giop_request_round_trip_via_giop_codec, crates/corba-ccm/src/dynamic_api.rs::tests::dsi_servant_default_dispatch_via_input_body, crates/corba-giop/src/object_ops.rs::tests::is_object_operation_recognizes_all_six_and_the_legacy_spelling, crates/corba-iiop/src/connection.rs::tests::round_trip_request_reply.

Status: done

§2.1 MIOP — extension of the IOP module

Spec: Part 2 §2.1, p. 2 — const ProfileId TAG_UIPMC = 3; const ComponentId TAG_GROUP = 39; const ComponentId TAG_GROUP_IIOP = 40.

Repo: crates/corba-ior/src/profile_tags.rs (ProfileId::Uipmc), crates/corba-ior/src/component_tags.rs (ComponentId::Group, ComponentId::GroupIiop).

Tests: crates/corba-ior/src/profile_tags.rs::tests::standard_profile_tag_values_match_spec, crates/corba-ior/src/component_tags.rs::tests::round_trip_all_known_tags.

Status: done

§6 Interoperability Overview

Spec: Part 2 §6, p. 7 — architecture overview of ORB interop.

Repo: —

Tests: —

Status: n/a (informative) — overview; the requirements are in §7–§12.

§7.1–§7.5 Domains, ORB services, bridging, object addressing

Spec: Part 2 §7.1–§7.5, pp. 15–24 — domains, ORB services, bridging between domains, interoperability approaches, domain-relative object references.

Repo: —

Tests: —

Status: n/a (informative) — architecture description; the fulfillable statements of §7 are in §7.6–§7.10.

§7.6 Interoperable Object References (IOR)

Spec: Part 2 §7.6, pp. 25–37 — IOR structure, TaggedProfile, standard profiles, TaggedComponent, standard components, composition, stringified IOR (IOR: + hex of the CDR encapsulation), object URLs corbaloc (iiop, rir, default port 2809, default version 1.0, IPv6 host in square brackets) and corbaname; failed conversion: BAD_PARAM with minor code 7 to 10.

Repo: crates/corba-ior/src/ior.rs, crates/corba-ior/src/tagged_profile.rs, crates/corba-ior/src/profile_tags.rs, crates/corba-ior/src/components.rs, crates/corba-ior/src/component_tags.rs, crates/corba-ior/src/stringified.rs, crates/corba-ior/src/url.rs.

Tests: crates/corba-ior/src/ior.rs::tests::round_trip_multi_profile_le, crates/corba-ior/src/ior.rs::tests::nil_ior_is_recognized, crates/corba-ior/src/tagged_profile.rs::tests::unknown_profile_tag_round_trips_as_other, crates/corba-ior/src/component_tags.rs::tests::well_known_component_tag_values_match_spec, crates/corba-ior/src/stringified.rs::tests::round_trip_be, crates/corba-ior/src/url.rs::tests::default_port_2809_when_missing, crates/corba-ior/src/url.rs::tests::rir_endpoint, crates/corba-ior/src/url.rs::tests::corbaname_with_fragment.

Status: partial — IOR, profiles, components, stringified IOR and corbaloc/corbaname are encoded and tested. Missing: an IPv6 host without a port, rir together with another protocol and the minor codes 7–10; own item.

§7.6.10 Object URLs — IPv6 without port, `rir` exclusion, minor codes

Spec: Part 2 §7.6.10, pp. 33–35 — <host> = DNS_style_host_name | IPv4_address | "[" IPv6_address "]", port optional with default 2809; “The rir protocol cannot be used with any other protocol in a URL”; “If conversion fails, string_to_object raises a BAD_PARAM exception” with minor code 7 (bad scheme name), 8 (bad address), 9 (bad schema specific part), 10 (non-specific reason).

Repo: —

Tests: —

Status: open — parse_endpoint in crates/corba-ior/src/url.rs splits the port off at the last colon; an IPv6 host without a port (corbaloc::[::1]/key) is cut apart and refused. A list with rir and iiop is accepted. Errors come as IorError, not as BAD_PARAM with a minor code.

§7.7 Service Context

Spec: Part 2 §7.7, pp. 37–40 — IOP::ServiceContext (context_id, context_data as a CDR encapsulation), standard IDs (§7.7.1), processing rules (§7.7.2): a context outside the own GIOP version or outside the OMG range may be ignored, but “must be passed on through a bridge and must be made available to interceptors. No exception shall be raised.”

Repo: crates/corba-giop/src/service_context.rs (ServiceContext, ServiceContextList, ServiceContextTag).

Tests: crates/corba-giop/src/service_context.rs::tests::standard_tag_values_match_spec, crates/corba-giop/src/service_context.rs::tests::round_trip_with_two_entries_be, crates/corba-giop/src/service_context.rs::tests::round_trip_le_byte_order.

Status: partial — encoding of the list and the standard IDs are tested; no test checks the processing rules of §7.7.2 (pass unknown or foreign-version contexts on without an exception and make them available to interceptors).

§7.8 Coder/Decoder Interfaces

Spec: Part 2 §7.8, pp. 40–43 — IOP::Codec (encode, decode, encode_value, decode_value) and IOP::CodecFactory::create_codec, reachable via resolve_initial_references("CodecFactory"); “The encodings which shall be supported are: ENCODING_CDR_ENCAPS, version 1.0; […] 1.1; […] 1.2”.

Repo: —

Tests: —

Status: open — no Codec and no CodecFactory in the tree.

§7.9 Feature Support and GIOP Versions

Spec: Part 2 §7.9, pp. 43–44, Table 7.2 — which service contexts, IOR components and features apply from which GIOP version 1.0 to 1.4.

Repo: crates/corba-giop/src/version.rs (Version::V1_0, V1_1, V1_2, supports_fragments, uses_flags_octet, uses_v1_2_request_layout, supports_bidirectional), crates/corba-iiop/src/profile_body.rs (components from IIOP 1.1).

Tests: crates/corba-giop/src/version.rs::tests::flags_octet_replaces_byte_order_at_1_1, crates/corba-giop/src/version.rs::tests::v1_2_request_layout_only_in_1_2_plus, crates/corba-iiop/src/profile_body.rs::tests::components_only_from_iiop_1_1.

Status: partial — the dependencies of GIOP 1.0 to 1.2 are implemented and tested; GIOP 1.3 and 1.4 are missing, own item.

§7.9 GIOP 1.3 and 1.4

Spec: Part 2 §7.9, pp. 43–44, Table 7.2 — columns V1.3 and V1.4.

Repo: —

Tests: —

Status: open — crates/corba-giop/src/version.rs knows only 1.0, 1.1 and 1.2.

§7.10 Code Set Conversion

Spec: Part 2 §7.10, pp. 45–58 — code set component of the IOR (TAG_CODE_SETS), negotiation of the transmission code set for char and wchar, CodeSets service context, OSF registry IDs, conversion of character data into the negotiated code set.

Repo: crates/corba-ior/src/components.rs (CodeSetComponentInfo::negotiate), crates/corba-giop/src/code_set.rs (CodeSetContext).

Tests: crates/corba-ior/src/components.rs::tests::negotiate_client_converts_to_server_native, crates/corba-ior/src/components.rs::tests::negotiate_universal_fallback, crates/corba-giop/src/code_set.rs::tests::well_known_ids_match_osf_registry, crates/corba-giop/src/code_set.rs::tests::service_context_roundtrip_via_list.

Status: partial — negotiation, service context and registry IDs are tested; conversion of character data into a negotiated code set other than UTF-8/UTF-16 is missing, own item.

§7.10 Conversion into a negotiated code set other than UTF-8/UTF-16

Spec: Part 2 §7.10.2, pp. 48–55 — client and server convert char and wchar data into the negotiated transmission code set (e.g. ISO 8859-1).

Repo: —

Tests: —

Status: open — crates/corba-giop/src/lib.rs describes the ISO-Latin conversion as the caller’s task; crates/wire/ encodes only UTF-8 and UTF-16.

§8 Building Inter-ORB Bridges

Spec: Part 2 §8, p. 63 — inline bridges, request-level bridges.

Repo: —

Tests: —

Status: n/a (informative) — Part 2 §8.1: “an implementation-oriented conceptual framework for the construction of bridges”; the clause states no requirement. The CORBA↔︎DDS bridge is covered in zerodds-corba-bridge-1.0.en.md.

§9 General Inter-ORB Protocol (GIOP)

Spec: Part 2 §9, p. 69 — GIOP wire protocol (all 8 message types), CDR transfer syntax, versioning 1.0/1.1/1.2, IIOP mapping, bi-dir GIOP.

Repo: crates/corba-giop/src/ with one file per message type plus crates/corba-giop/src/header.rs, crates/corba-giop/src/codec.rs, crates/corba-giop/src/service_context.rs, crates/corba-giop/src/target_address.rs, crates/corba-giop/src/flags.rs, crates/corba-giop/src/version.rs.

Tests: crates/corba-giop/src/codec.rs::{round_trip_request_giop_1_0_be, round_trip_request_giop_1_2_le, giop_1_2_body_is_eight_aligned_from_the_message_start, giop_1_0_body_is_not_padded, header_message_size_matches_actual_body, message_size_larger_than_the_buffer_is_refused}, crates/corba-giop/src/header.rs::{magic_bytes_match_spec, header_size_is_12_bytes, round_trip_big_endian_request_header, round_trip_little_endian_reply_header}, crates/corba-giop/src/version.rs::{version_constants_match_spec, flags_octet_replaces_byte_order_at_1_1, v1_2_request_layout_only_in_1_2_plus}.

Status: done

§9.3 CDR Transfer Syntax

Spec: §9.3, p. 71 — CDR encoding, endianness marking, primitive/construct layout, GIOP 1.2 alignment.

Repo: crates/wire/src/writer.rs + crates/wire/src/reader.rs (primitives + alignment + encapsulation), re-used by the GIOP codec in crates/corba-giop/src/codec.rs.

Tests: crates/corba-giop/src/codec.rs::{giop_1_2_body_is_eight_aligned_from_the_message_start, giop_1_2_reply_body_is_eight_aligned_from_the_message_start, giop_1_0_body_is_not_padded}, crates/corba-giop/src/request.rs::tests::giop_1_2_request_body_is_8_aligned, crates/corba-giop/src/service_context.rs::{round_trip_with_two_entries_be, round_trip_le_byte_order}.

Status: done

§9.4 GIOP Message Formats

Spec: §9.4, p. 93 — all 8 message types with binary layout (Request/Reply/CancelRequest/LocateRequest/LocateReply/ CloseConnection/MessageError/Fragment).

Repo: one file per message type in crates/corba-giop/src/ — crates/corba-giop/src/request.rs, crates/corba-giop/src/reply.rs, crates/corba-giop/src/cancel_request.rs, crates/corba-giop/src/locate_request.rs, crates/corba-giop/src/locate_reply.rs, crates/corba-giop/src/close_connection.rs, crates/corba-giop/src/message_error.rs, crates/corba-giop/src/fragment.rs.

Tests: one octet round trip per message type — crates/corba-giop/src/request.rs::{round_trip_giop_1_0_request, round_trip_giop_1_1_request_with_reserved_bytes, round_trip_giop_1_2_request_with_target_address}, crates/corba-giop/src/reply.rs::{round_trip_giop_1_0_no_exception, round_trip_giop_1_2_user_exception, round_trip_location_forward_perm_in_1_2}, crates/corba-giop/src/cancel_request.rs::tests::round_trip, crates/corba-giop/src/locate_request.rs::{round_trip_giop_1_0, round_trip_giop_1_2_with_profile_addr}, crates/corba-giop/src/locate_reply.rs::{round_trip_giop_1_0_object_here, round_trip_giop_1_2_object_forward_perm}, crates/corba-giop/src/fragment.rs::{round_trip_giop_1_2_with_header, round_trip_giop_1_1_without_header}. All eight through the whole-message codec, CloseConnection and MessageError (no body) only there: crates/corba-giop/src/codec.rs::{round_trip_request_giop_1_0_be, round_trip_close_connection, round_trip_message_error, round_trip_fragment_with_more_bit, round_trip_cancel_request, round_trip_locate_request_giop_1_2, round_trip_locate_reply_object_here}. The type discriminators themselves: crates/corba-giop/src/message_type.rs::tests::message_type_values_match_spec_table_15_1.

Status: done

§9.5 GIOP Message Transport

Spec: §9.5, p. 107 — transport requirements (ordered, lossless), connection management.

Repo: crates/corba-iiop/src/connection.rs, crates/corba-iiop/src/acceptor.rs, crates/corba-iiop/src/connector.rs for TCP transport.

Tests: crates/corba-iiop/src/acceptor.rs::tests::round_trip_via_acceptor_and_connector, crates/corba-iiop/src/connection.rs::{round_trip_request_reply, shutdown_propagates_eof_to_peer, close_connection_message_round_trip}, crates/corba-iiop/src/framing.rs::tests::read_back_to_back_messages (message boundaries in the stream), crates/corba-iiop/src/connector.rs::{connect_reuses_pooled_connection, invalidated_connection_is_not_returned_to_pool, max_connections_per_endpoint_is_enforced}.

Status: done — TCP via IIOP. Other transport bindings (e.g. SCTP) not offered.

§9.6 Object Location

Spec: §9.6, p. 110 — LocateRequest/LocateReply semantics, forward- ing.

Repo: crates/corba-giop/src/locate_request.rs, crates/corba-giop/src/locate_reply.rs.

Tests: crates/corba-giop/src/locate_reply.rs::{locate_status_values_match_spec, round_trip_giop_1_0_object_here, round_trip_giop_1_2_object_forward_perm, forward_perm_in_1_0_is_rejected}, crates/corba-giop/src/locate_request.rs::{round_trip_giop_1_0, round_trip_giop_1_2_with_profile_addr, giop_1_0_rejects_profile_target}.

Status: done

§9.7 Internet Inter-ORB Protocol (IIOP)

Spec: §9.7, p. 111 — IIOP as TCP mapping; IIOP::ProfileBody (host/port/object key + TaggedComponents).

Repo: crates/corba-iiop/src/profile_body.rs, crates/corba-iiop/src/framing.rs, crates/corba-iiop/src/acceptor.rs, crates/corba-iiop/src/connector.rs, crates/corba-iiop/src/connection.rs.

Tests: crates/corba-iiop/src/profile_body.rs::{iiop_version_constants_match_spec, components_only_from_iiop_1_1, round_trip_v1_0_be, round_trip_v1_0_le, round_trip_v1_2_with_components, v1_0_does_not_emit_components_field}, crates/corba-iiop/src/framing.rs::{round_trip_request_through_cursor, round_trip_reply_le, outbound_fragmentation_be_le_many_fragments, fragment_reassembly_three_fragments, oversized_message_size_is_rejected_cleanly}.

Status: done

§9.8/§9.9 Bi-Directional GIOP

Spec: §9.8 + §9.9, pp. 115-118 — BiDirIIOP service context, BiDirGIOP policy.

Repo: crates/corba-iiop/src/bidir.rs (wire codec) + crates/corba-ccm/src/orb_extensions.rs::{BiDirPolicy, BiDirServiceContext} (policy lifecycle: Normal/Both; listen_points list for §9.9.1).

Tests: inline tests in bidir.rs + orb_extensions::tests::{bidir_policy_distinct, bidir_service_context_listen_points}.

Status: done — BiDir codec + policy lifecycle live.

§9.10 OMG IDL for GIOP

Spec: §9.10, p. 119 — IDL for GIOP module constants + service context IDs.

Repo: as Rust constants in crates/corba-giop/src/service_context.rs (ServiceContextTag), crates/corba-giop/src/message_type.rs (MessageType), crates/corba-giop/src/flags.rs (Flags), crates/corba-giop/src/version.rs (Version), crates/corba-giop/src/reply.rs (ReplyStatusType), crates/corba-giop/src/locate_reply.rs (LocateStatusType), crates/corba-giop/src/target_address.rs (AddressingDisposition).

Tests: one value comparison against the IDL per constant group — crates/corba-giop/src/service_context.rs::tests::standard_tag_values_match_spec, crates/corba-giop/src/message_type.rs::tests::message_type_values_match_spec_table_15_1, crates/corba-giop/src/flags.rs::{fragment_bit_value_matches_spec, byte_order_bit_value_matches_spec}, crates/corba-giop/src/version.rs::tests::version_constants_match_spec, crates/corba-giop/src/reply.rs::tests::reply_status_values_match_spec, crates/corba-giop/src/locate_reply.rs::tests::locate_status_values_match_spec, crates/corba-giop/src/target_address.rs::tests::disposition_values_match_spec.

Status: done

§10 Secure Interoperability (CSIv2)

Spec: Part 2 §10, p. 125 — Common Secure Interoperability v2: SAS protocol, GSSUP token, transport mechanisms (TLS), authorization tokens, IOR components (TAG_CSI_SEC_MECH_LIST).

Repo: crates/corba-csiv2/ with sas.rs, gssup.rs, mech_list.rs, association_options.rs; IOR tag codec in crates/corba-ior/src/component_tags.rs.

Tests: crates/corba-csiv2/src/sas.rs::tests (9 tests): sas_msg_type_values_match_spec, sas_context_body_roundtrip_all_messages_be_le, server_eval_decodes_foreign_gss_wrapped_establish_context, identity_token_discriminator_matches_spec, establish_context_holds_full_payload, complete_context_indicates_stateful, context_error_carries_gss_status; crates/corba-csiv2/src/session.rs::tests (9), among them a_stateful_target_answers_establish_with_a_stateful_complete, a_full_session_survives_the_wire_in_both_byte_orders; crates/corba-csiv2/src/gssup.rs::tests::gssup_byte_identical_to_jacorb, ::initial_context_token_tag_is_0x60, ::encapsulation_is_wire_correct_octet_seq_len_at_offset_4.

Status: done

§10.2 Protocol Message Definitions

Spec: §10.2, p. 127 — SAS message codec (EstablishContext, CompleteEstablishContext, ContextError, MessageInContext).

Repo: crates/corba-csiv2/src/sas.rs (SasMessage with encode_encapsulation/decode_encapsulation, IdentityToken).

Tests: crates/corba-csiv2/src/sas.rs::{sas_msg_type_values_match_spec, sas_context_body_roundtrip_all_messages_be_le, sas_identity_token_absent_anonymous_roundtrip, identity_token_discriminator_matches_spec, establish_context_holds_full_payload, complete_context_indicates_stateful, message_in_context_can_request_discard, context_error_carries_gss_status}.

Status: done

§10.3 Security Attribute Service (SAS)

Spec: §10.3, p. 137 — SAS state machine, stateful/stateless contexts.

Repo: crates/corba-csiv2/src/session.rs::{SasTarget, SasClient, TargetAction, RetainedContext, CONTEXT_ERROR_NO_CONTEXT, CONTEXT_ERROR_INVALID_EVIDENCE} — the target and client halves of the state machine over the SasMessage types of §10.2. A stateful target retains the context under its ContextId and the client then sends MessageInContext instead of fresh credentials, until a discard_context or a ContextError puts it back into the establish state.

Tests: crates/corba-csiv2/src/session.rs::{a_stateful_target_answers_establish_with_a_stateful_complete, a_stateless_target_retains_nothing_and_says_so, the_second_request_on_a_stateful_context_is_a_message_in_context, a_stateless_client_re_establishes_on_every_request, discarding_a_context_makes_the_next_reference_to_it_a_context_error, a_message_in_context_for_an_unknown_id_is_refused, a_context_error_puts_the_client_back_into_the_establish_state, a_target_to_client_message_arriving_at_a_target_is_not_evidence, a_full_session_survives_the_wire_in_both_byte_orders}.

Status: done — the last test drives the whole session over the §10.2 octets: every message crosses encode_encapsulation / decode_encapsulation before the other half sees it.

§10.4 Transport Security Mechanisms

Spec: §10.4, p. 149 — TLS/SSL bindings, mutual auth.

Repo: TLS stack via crates/security-pki/ (X.509 + TLS). CSIv2-→-IIOP-TLS bind via crates/corba-csiv2::association_options + crates/corba-iiop acceptor (TAG_TLS_SEC_TRANS profile tags in crates/corba-ior/src/component_tags.rs); the glue is bound in the acceptor lifecycle.

Tests: crates/corba-csiv2/src/mech_list.rs::tests: build_mech_list_with_tls_and_gssup, empty_list_has_no_mechanisms, cdr_roundtrip_compound_sec_mech_list, octet_seq_seq_rejects_oversized_count, compound_sec_mech_list_rejects_oversized_count, cdr_roundtrip_empty_list; crates/corba-csiv2/src/association_options.rs::tests::flag_values_match_spec_table_24_1, ::has_and_with_round_trip; crates/corba-ior/src/component_tags.rs::tests::well_known_component_tag_values_match_spec, ::round_trip_all_known_tags, ::at_least_32_well_known_tags_modelled.

Status: done — TLS stack + CSIv2-IIOP bind via IOR tags live.

§10.5 Interoperable Object References (IOR with security tags)

Spec: §10.5, p. 150 — IOR format with TAG_CSI_SEC_MECH_LIST, TAG_NULL_TAG, TAG_TLS_SEC_TRANS.

Repo: crates/corba-ior/src/component_tags.rs (ComponentId with CsiSecMechList = 33, NullTag = 34, TlsSecTrans = 36), crates/corba-ior/src/components.rs (StructuredComponent), crates/corba-csiv2/src/mech_list.rs (CompoundSecMechList).

Tests: crates/corba-ior/src/ior.rs::tests::a_security_ior_carries_mech_list_tls_and_null_tag_through_a_round_trip — a complete IOR carrying the three tags in the IIOP profile’s component list, through encode_encapsulation/decode_encapsulation and back into the structured form. Tag values and the component bodies on their own: crates/corba-ior/src/component_tags.rs::{well_known_component_tag_values_match_spec, round_trip_all_known_tags, at_least_32_well_known_tags_modelled}, crates/corba-ior/src/components.rs::{csi_sec_mech_list_round_trip, tls_sec_trans_with_addresses_round_trip, ssl_sec_trans_round_trip}.

Status: done

§10.6 Conformance Levels (CSIv2)

Spec: §10.6, p. 160 — four CSIv2 conformance levels (0-3).

Repo: the mechanisms implemented in corba-csiv2 cover all three normative levels (0/1/2); conformance markers in crates/corba-ccm/src/lib.rs::conformance::{CORBA_PART2_10_6_CSIV2_LEVEL_0, CORBA_PART2_10_6_CSIV2_LEVEL_1, CORBA_PART2_10_6_CSIV2_LEVEL_2}.

Tests: conformance_tests::csiv2_level_markers_match_spec.

Status: done — conformance markers explicitly stated for all three levels.

§10.7 Sample Message Flows and Scenarios

Spec: §10.7, p. 162 — examples.

Repo: —

Tests: —

Status: n/a (informative) — sample flows.

§10.8 References

Spec: §10.8, p. 171 — reference list.

Repo: —

Tests: —

Status: n/a (informative) — reference list.

§10.9 IDL for CSIv2

Spec: §10.9, p. 172 — IDL of the CSI modules.

Repo: as Rust representation in crates/corba-csiv2/src/association_options.rs (AssociationOptions), crates/corba-csiv2/src/mech_list.rs (CompoundSecMechList, CompoundSecMech, AsContextSec, SasContextSec), crates/corba-csiv2/src/sas.rs (SasMsgType, IdentityToken, the SASContextBody union as SasMessage), crates/corba-csiv2/src/gssup.rs (GssupCredentialToken).

Tests: one value/layout comparison against the IDL per module — crates/corba-csiv2/src/association_options.rs::tests::flag_values_match_spec_table_24_1, crates/corba-csiv2/src/sas.rs::{sas_msg_type_values_match_spec, identity_token_discriminator_matches_spec}, crates/corba-csiv2/src/mech_list.rs::{cdr_roundtrip_compound_sec_mech_list, build_mech_list_with_tls_and_gssup, cdr_roundtrip_empty_list}, crates/corba-csiv2/src/gssup.rs::{initial_context_token_tag_is_0x60, gssup_oid_starts_with_der_tag, encapsulation_is_wire_correct_octet_seq_len_at_offset_4}.

Status: done

§11 Unreliable Multicast Inter-ORB Protocol (MIOP)

Spec: Part 2 §11, p. 181 — UDP multicast variant of GIOP for unreliable group communication.

Repo: crates/corba-ccm/src/orb_extensions.rs::{MiopConfig, MiopFrameHeader, MiopError, MulticastSink, MulticastSinkError, MiopSender, MIOP_MAGIC, MIOP_VERSION_1_0} with IPv4 multicast group + port + TTL + loopback flag (default 239.255.0.1:5683 TTL=1) plus full MIOP frame codec (16-byte header incl. MIOP magic bytes, version 0x10, flags endian/last-frag bit, packet length, unique ID, packet number, number-of-packets) and MiopSender::send_giop, which sends GIOP bytes as a single packet resp. multi-packet set via a MulticastSink adapter (adapter trait, so that corba-ccm creates no transport-udp layer cycle).

Tests: orb_extensions::tests::{miop_config_default_uses_239_range, miop_frame_encode_decode_roundtrip, miop_frame_decode_rejects_bad_magic_and_version, miop_sender_single_packet_fits_mtu, miop_sender_fragments_multi_packet_over_small_mtu}.

Status: done — MIOP frame codec + sender path with single-/ multi-packet fragmentation + multicast-sink adapter trait..

§12 ZIOP Protocol

Spec: Part 2 §12, p. 219 — Zlib/compress-IOP messages, compression policies.

Repo: crates/corba-ccm/src/orb_extensions.rs::ZiopConfig + CompressionAlgorithm (see §18 Compression).

Tests: crates/corba-ccm/src/orb_extensions.rs::tests::compression_algorithm_round_trip, ::compression_zlib_round_trip, ::compression_gzip_round_trip, ::compression_deflate_round_trip.

Status: done — ZIOP config data model + production compression codec (cross-ref §18 Compression). ZiopConfig.algorithm selects the codec from the backends (None/Zlib/Gzip/Deflate); LZMA remains explicitly unsupported.

Part 3: Component Model (CCM)

§1, §3–§5 Scope/References/Terms/Symbols

Spec: Part 3 §1, §3–§5, pp. 1-7 — scope, references, terms, symbols.

Repo: —

Tests: —

Status: n/a (informative) — scope, reference lists and terms.

§2 Conformance and Compliance

Spec: Part 3 §2, pp. 1–3 — compliance points: Basic Level (for non-Java products IDL extensions, CIDL without segments, a container, XML deployment descriptors), Java Basic Level (EJB 1.1, RMI/IIOP, EJB-to-IDL), Extended Level, Lightweight CCM profile, EJB clients (optional), Generic Interaction Support (porttype, mirrorport, port, templates, connectors, D&C extensions).

Repo: crates/corba-ccm/src/container.rs, crates/corba-ccm/src/cidl.rs, crates/corba-ccm-ejb/, crates/corba-ccm-lib/.

Tests: crates/corba-ccm/src/container.rs::tests::install_and_full_lifecycle_round_trip.

Status: partial — container, component model, EJB integration and the Lightweight profile are items §6–§17; the Basic Level lacks the CIDL parser (item “§8 OMG CIDL — remaining constructs”, open).

§6 Component Model

Spec: Part 3 §6, p. 9 — component definition, facets, receptacles, events, homes, home finders, configuration, inheritance, conformance.

Repo: crates/corba-ccm/src/component_def.rs, crates/corba-ccm/src/home.rs, crates/corba-ccm/src/port.rs, crates/corba-ccm/src/context.rs, crates/corba-ccm/src/lifecycle.rs.

Tests: crates/corba-ccm/src/component_def.rs::tests (30 tests), among them trader_has_4_ports, keyed_component_detected, provide_facet_returns_facet_by_name, get_all_facets_returns_complete_list, get_all_publishers_excludes_emit_only_sources, supports_interface_returns_true_for_listed_iface, the_base_chain_runs_from_the_derived_component_to_the_root, flattening_takes_over_every_inherited_feature_bases_first, a_redefined_port_name_is_refused_rather_than_shadowed, a_second_primary_key_in_the_chain_is_refused; crates/corba-ccm/src/cidl.rs::tests::all_four_composition_categories_distinct; the sub-items §6.5-§6.13 name one test per clause each.

Status: done

Spec: Part 3 §17, p. 343 — XML schema for deployment plans.

Repo: crates/corba-dnc/src/xml.rs.

Tests: crates/corba-dnc/src/xml.rs::{parses_minimal_plan, parses_multiple_artifacts, validation_fails_on_unknown_impl_reference, missing_root_tag_returns_expected_tag, co_locate_with_parsed}.

Status: done

Adjacent OMG service: COS Naming v1.3 (formal/04-10-03)

The CosNaming service is its own spec, carried here as an initial reference per Part 1 §8.5.2.

CosNaming::NamingContext

Spec: CosNaming v1.3 §2 — bind/rebind/unbind/resolve/ new_context, iterator-based list(), stringified names ("a/b/c" pattern via NamingContextExt::resolve_str).

Repo: crates/corba-cosnaming/src/context.rs, crates/corba-cosnaming/src/name.rs, crates/corba-cosnaming/src/stringified.rs.

Tests: crates/corba-cosnaming/src/context.rs::tests (13 tests): bind_and_resolve_simple, double_bind_yields_already_bound, rebind_replaces_existing, nested_context_resolve, resolve_to_context_returns_context, resolve_unknown_yields_missing_node, unbind_removes_entry, destroy_with_bindings_yields_not_empty, destroy_empty_is_ok, list_returns_all_bindings_with_correct_type, resolve_str_via_naming_context_ext, to_url_constructs_corbaname, empty_name_is_invalid; crates/corba-cosnaming/src/stringified.rs::tests (9), crates/corba-cosnaming/src/name.rs::tests (3).

Status: done

ZeroDDS-specific bridges (no OMG item)

CORBA object ↔︎ DDS topic bridge

Spec: no OMG spec item; ZeroDDS-specific migration layer for the incremental replacement of CORBA endpoints by DDS wire.

Repo: crates/corba-dds-bridge/src/mapping.rs (IOR↔︎topic+instance), crates/corba-dds-bridge/src/servant.rs (CORBA servant over DDS-RPC), crates/corba-dds-bridge/src/sync.rs.

Tests: crates/corba-dds-bridge/src/mapping.rs::tests (6 tests): add_and_lookup_route, lookup_unknown_yields_none, operation_mapping_by_name, add_route_replaces_existing, all_routes_listing, direction_variants_distinct; crates/corba-dds-bridge/src/locate.rs::tests (4), crates/corba-dds-bridge/src/notify.rs::tests (4), crates/corba-dds-bridge/src/csiv2_wire.rs::tests (4), crates/corba-dds-bridge/src/bridge_security.rs::tests (5).

Status: done — informative; not spec-bound.

Audit status

51 done / 6 partial / 6 open / 0 blocked / 12 n/a (informative).

Test run:

cargo test -p zerodds-corba-giop --lib — 80 tests green.
cargo test -p zerodds-corba-iiop --lib — 38 tests green.
cargo test -p zerodds-corba-ior --lib — 53 tests green.
cargo test -p zerodds-corba-poa --lib — 39 tests green.
cargo test -p zerodds-corba-cosnaming --lib — 25 tests green.
cargo test -p zerodds-corba-csiv2 --lib — 35 tests green.
cargo test -p zerodds-corba-cos-event --lib — 23 tests green.
cargo test -p zerodds-corba-ccm --lib — 181 tests green.
cargo test -p zerodds-corba-ccm-lib --lib — 23 tests green.
cargo test -p zerodds-corba-ccm-ejb --lib — 25 tests green.
cargo test -p zerodds-corba-ir --lib — 23 tests green.
cargo test -p zerodds-corba-dnc --lib — 30 tests green.
cargo test -p zerodds-corba-dds-bridge --lib — 43 tests green.
cargo test -p zerodds-corba-codegen --tests — 38 + 15 + 10 tests green.
cargo test -p zerodds-idl-parse --tests — 36 + 32 tests green.
cargo test -p zerodds-idl-lower --tests — 5 + 49 + 23 + 12 + 36 + 4 + 82 + 3 + 62 tests green.

Open items: corba-3.3.open.en.md.

OMG CORBA 3.3 — Spec-Coverage (WP CORBA-Coexistence)

Quelle: OMG CORBA 3.3 — drei Bände als formal-Dokumente: * Part 1 (Interfaces, 532 S.) — formal/12-11-12 * Part 2 (Interoperability, 249 S.) — formal/12-11-14 * Part 3 (Component Model, 380 S.) — formal/12-11-16

Kontext. ZeroDDS deckt mit dem DDS-Kern und dem Codegen aus crates/lang-rules/ und crates/corba-codegen/ das DDS-PSM vollständig ab. Für die Migration von Bestands-CORBA-Anwendungen in der Finanzindustrie soll ZeroDDS als Drop-in-Backend auftretbar sein: ein bestehender CORBA-Client kompiliert und linkt gegen Annex-A.1-Stubs, läuft gegen ZeroDDS-Endpoints, die GIOP/IIOP-Wire sprechen, und kann schrittweise auf reines DDS migriert werden ohne ad-hoc Infrastruktur-Tausch.

Die CORBA-Coexistence ist über mehrere Implementierungs-Crates verteilt:

crates/idl-parse/ · docs.rs — IDL-Grammatik (Part 1 §7 IDL-Syntax)
crates/corba-codegen/ · docs.rs — Annex-A.1-Codegen (Stubs/Skeletons, Part 1 §7)
crates/corba-ir/ · docs.rs — Interface Repository (Part 1 §14)
crates/corba-poa/ · docs.rs — Portable Object Adapter (Part 1 §15)
crates/corba-giop/ · docs.rs — GIOP-Wire-Protokoll (Part 2 §9)
crates/corba-iiop/ · docs.rs — IIOP-Transport (Part 2 §9.7)
crates/corba-ior/ · docs.rs — IOR-Kodierung (Part 2 §9.4 / §10.5)
crates/corba-csiv2/ · docs.rs — CSIv2-Security (Part 2 §10)
crates/corba-ccm/ · docs.rs — Component Model (Part 3 §6-§9)
crates/corba-ccm-lib/ · docs.rs — CCM-Container (Part 3 §10)
crates/corba-ccm-ejb/ · docs.rs — EJB-Integration (Part 3 §11)
crates/corba-dnc/ · docs.rs — Deployment & Configuration (Part 3 §15-§17)
crates/corba-dds-bridge/ · docs.rs — ZeroDDS-Bridge (kein OMG-Item)
crates/corba-cosnaming/ · docs.rs — COS Naming v1.3 (separate Spec)
crates/corba-cos-event/ · docs.rs — COS Event Service v1.2 (separate Spec)
crates/dcps/ · docs.rs — DDS-PSM-Kern (DDS-Migrationsziel)
crates/rpc/ · docs.rs — DDS-RPC-Kern (DDS-Migrationsziel)

§8 ORB Interface

Spec: Part 1 §8, S. 93 — ORB-Pseudo-Objekt: ORB_init, string_to_object/object_to_string, resolve_initial_references, Policy-Management, TypeCodes, Standard-Exceptions.

Repo: crates/corba-ior/src/stringified.rs (string↔︎IOR), crates/corba-ior/src/url.rs (corbaloc/corbaname), crates/corba-poa/src/policies.rs (Policy-Set für POA-Scope), crates/corba-ir/src/type_code.rs (TypeCode-Repräsentation), crates/corba-giop/src/error.rs + crates/corba-poa/src/error.rs (Standard-Exceptions als Rust-Result).

Status: done — String-↔︎-IOR und URL-Schemes (§8.2.2, §8.5.2) abgedeckt; ORB-Singleton-Lifecycle (Orb::init/shutdown/destroy), Threading-Operations (ThreadingMode::SingleThreaded/ThreadPerRequest/ ThreadPool), Policy-Domain-Manager (Orb::set_policy/get_policy) in crates/corba-ccm/src/orb_core.rs. Standard-Exceptions als Rust-Result-Layer.

§9 Value Type Semantics

Spec: Part 1 §9, S. 155 — Valuetype-Marshaling (CDR-Repräsentation, Boxed-Value, Custom Marshaling, Sending-Context-Run-Time).

Repo: crates/wire/src/writer.rs + crates/wire/src/reader.rs (Codec-Basis), crates/idl-parse/src/decl.rs (parse_valuetype, Value-Box und custom valuetype), crates/lang-rules/src/coverage.rs (Valuetype-Regel je Zielsprache), kein dediziertes Custom-Marshal-Hook im Codegen.

Status: done — Valuetype-IDL parst, lowert und trägt in lang-rules eine Emissions-Regel je Zielsprache; Valuetype und Valuebox tragen in allen vier PSM-Spalten die Member, die Annex A.1.1 ihnen gibt. Custom-Marshal-Streams via crates/corba-ccm/src/orb_core.rs::StreamableValue-Trait (marshal/unmarshal/repository_id); Sending-Context-Run-Time via SendingContext mit code_set + truncation_codebase.

§10 Abstract Interface Semantics

Spec: Part 1 §10, S. 171 — abstract interface, Marshalling als Object oder ValueType.

Repo: crates/idl-parse/src/decl.rs (abstract gehört zu zwei Produktionen — Interface-Header (79) und <value_abs_def> (127); die Weiche steht in parse_definition), Codegen-Zeile in crates/corba-codegen/tests/orb-corpus/rows/03-abstractbase.idl.

Status: done — Parser akzeptiert abstract interface, das Lowering führt es als eigenen Interface-Kind, und der Codegen-Korpus enthält die Zeile.

§11 Dynamic Invocation Interface (DII)

Spec: Part 1 §11, S. 175 — Request/NVList/NamedValue-API für dynamische Methoden-Aufrufe ohne kompilierten Stub.

Repo: crates/corba-ccm/src/dynamic_api.rs::{Request, NvList, NamedValue, ArgFlag} mit add_in_arg/add_out_arg-Operations, ArgFlag::{In, Out, InOut} (Spec §11.1.2 Wire-Werte 1/2/3) und NVList-add_value/count (Spec §11.1.3).

Status: done — Daten-Modell + Wire-up: Request::encode_giop_request(request_id, object_key) liefert ein corba_giop::Request-Frame mit konkatenierten In/InOut- Args; Roundtrip via corba_giop::encode_message + decode_message ist getestet. Spec §11.2 + §15.4.2.

§12 Dynamic Skeleton Interface (DSI)

Spec: Part 1 §12, S. 191 — ServerRequest-Pseudo-Objekt für generische Server-Implementations.

Repo: crates/corba-ccm/src/dynamic_api.rs::ServerRequest mit set_result(value)/set_exception(id, value)-Operations.

Tests: dynamic_api::tests::{dsi_server_request_set_result, dsi_server_request_set_exception, dsi_input_body_concatenates_in_and_inout, dsi_servant_default_dispatch_via_input_body}.

Status: done — ServerRequest-Daten-Modell + DsiServant-Trait (Spec §12) als generischer Server-Side-Dispatch-Pfad. Wegen Layer- Trennung (corba-ccm Layer 8.3 / corba-poa Layer 8.16) ist der Trait orthogonal zu corba-poa::Servant definiert und kann zusätzlich implementiert werden. ServerRequest::input_body() konkateniert In/InOut-Args zu einem flachen Body; ein Mock-Servant in den Tests zeigt den Echo-Roundtrip.

§13 Dynamic Management of Any Values (DynAny)

Spec: Part 1 §13, S. 195 — DynAny-API zum Iterieren über any- Inhalte ohne TypeCode-spezifische Codegen.

Repo: crates/corba-ccm/src/dynamic_api.rs::{DynAny, DynAnyKind} mit equal/from_any/to_any-Operations + Type-Discriminator-Enum (Spec §13.1: Primitive/Struct/Union/Enum/Sequence/Array/Fixed/ Value/ValueBox).

Status: done — DynAny-Daten-Modell + Wire-up from_type_code(tc, raw) walked einen corba_ir::TypeCode über CDR-any-Bytes; primitive Typen (Long/ULong/Short/Boolean/String/…) werden via zerodds_wire::Reader validiert (Decode-Fehler werden propagiert), komplexe Typen (Struct/Sequence/Array) preserven die rohen Bytes plus Repository-ID. to_cdr() projiziert die DynAny zurück.

§14 The Interface Repository

Spec: Part 1 §14, S. 219 — IR als CORBA-Service mit Container/ Contained/IDLType Interface-Hierarchie; Repository-IDs; Component-IR-Erweiterungen (Part 3); IDL des IR.

Repo: crates/corba-ir/src/repository.rs (Repository, Container-Hierarchie), crates/corba-ir/src/repository_id.rs (IDL-/Local-Format Repository-IDs), crates/corba-ir/src/type_code.rs (TypeCode-Backend), crates/corba-ir/src/definition_kind.rs (DK_*).

Tests: crates/corba-ir/src/repository.rs::tests (11 Tests): scoped_lookup_descends_hierarchy, absolute_name_builds_scoped_path, operation_def_carries_typed_signature, interface_def_details, register_and_lookup_id, duplicate_id_yields_error, lookup_name_at_top_level, nested_module_lookup_name_recurses, describe_contents_filters_by_kind, definition_carries_type_code, remove_deletes_definition; crates/corba-ir/src/definition_kind.rs::tests::well_known_definition_kinds_match_spec, ::at_least_26_kinds_modeled; crates/corba-ir/src/repository_id.rs::tests::round_trip_omg_namingcontext, ::missing_idl_prefix_is_invalid, ::missing_version_is_invalid.

Status: done — IR-Interface-Hierarchie + RepositoryIds + TypeCodes implementiert. Component-IR-Erweiterungen siehe Part 3 §12 (CCM- Metamodel).

§15 The Portable Object Adapter (POA)

Spec: Part 1 §15, S. 301 — POA-Architektur: Policies (Lifespan, IdAssignment, IdUniqueness, ServantRetention, RequestProcessing, ImplicitActivation, Thread), Object-Activation, Servant-Manager, Adapter-Activator, POA-Hierarchie, IDL für PortableServer.

Repo: crates/corba-poa/src/poa.rs (Hierarchie + Dispatch), crates/corba-poa/src/policies.rs (alle 7 Standard-Policies), crates/corba-poa/src/active_object_map.rs (AOM), crates/corba-poa/src/servant.rs + crates/corba-poa/src/servant_manager.rs, crates/corba-poa/src/object_id.rs, crates/corba-poa/src/poa_manager.rs (Aktivierungs-Lifecycle).

Tests: crates/corba-poa/src/poa.rs::tests (12 Tests): poa_hierarchy_create_find_destroy, default_root_dispatch_via_aom, user_id_activation_with_explicit_oid, use_default_servant_falls_back_to_default, use_servant_manager_with_activator_caches_in_aom, non_retain_with_locator_calls_pre_post_per_invocation, dispatch_in_holding_state_is_rejected, dispatch_in_inactive_state_yields_adapter_inactive, dispatch_in_discarding_state_returns_obj_adapter, invalid_policy_combination_is_rejected_at_construction; crates/corba-poa/src/active_object_map.rs::tests (6), crates/corba-poa/src/policies.rs::tests (8), crates/corba-poa/src/poa_manager.rs::tests::full_state_cycle, crates/corba-poa/src/object_id.rs::tests::system_id_is_8_bytes_big_endian, crates/corba-poa/src/servant.rs::tests::is_a_checks_repository_ids, crates/corba-poa/src/servant_manager.rs::tests::locator_preinvoke_returns_servant_and_cookie.

Status: done — alle 7 Standard-Policies + Servant-Manager-Pfad + AOM + POA-Hierarchie + Dispatch implementiert. Adapter-Activator (§15.3.6) als ServantManager-Variante mitabgedeckt; falls strikte Trennung verlangt, wäre das ein kleiner Refactor (≤0.5 PW).

§16 Portable Interceptors

Spec: Part 1 §16, S. 357 — Client-/Server-Request-Interceptor-API, PolicyFactory-Registrierung, IORInterceptor (TaggedComponent-Inject), PI-Initial-Reference (PICurrent).

Repo: crates/corba-ccm/src/orb_extensions.rs::{ClientRequestInterceptor, ServerRequestInterceptor, IorInterceptor, InterceptorRegistry, PolicyFactory, PiCurrent, ClientInterceptionPoint, ServerInterceptionPoint} mit allen 5 Client-Points (send_request/send_poll/receive_reply/receive_exception/ receive_other) + 5 Server-Points (receive_request_service_contexts/ receive_request/send_reply/send_exception/send_other) + Registry + PiCurrent-Slot-Storage. Pipeline-Walks (walk_client, walk_server, walk_ior) sind in crates/corba-iiop/src/connection.rs:: Connection::with_interceptors verdrahtet: read_message/ write_message walken automatisch SendRequest/ReceiveReply (Client) bzw. ReceiveRequest/SendReply (Server) wenn eine Registry installiert ist.

Status: done — PI-Daten-Modell + Pipeline-Integration in IIOP-Connection-Send/Receive-Pfad.

§17 CORBA Messaging

Spec: Part 1 §17, S. 415 — Asynchrone Messaging (AMI), Time- Independent Invocations (TII), QoS-Policies (RebindPolicy, SyncScopePolicy etc.).

Repo: crates/corba-ccm/src/orb_extensions.rs::{MessagingPolicy, AmiReplyHandler, AmiReplySink, dispatch_async_reply, PersistentRequestStore, PersistentRequestEntry} mit allen 10 Policy-Types (Rebind/SyncScope/RequestPriority/ReplyPriority/Routing/ MaxHops/RequestTime/ReplyTime/RelativeRoundtripTimeout/ RoutingTypeRange) + Wire-Mapping policy_type() -> u32 nach OMG Messaging.idl (formal/2011-11-02 §B.5.1). AMI-Reply-Dispatch (dispatch_async_reply) mappt einen corba_giop::Reply auf die drei Spec-Callbacks handle_reply / handle_excep / handle_other. TII (Time-Independent-Invocations) liefert PersistentRequestStore mit add / poll / timeout_expired.

Status: done — AMI-Reply-Dispatch-Bridge auf corba_giop::Reply + TII Persistent-Request-Store + Wire-Mapping aller 10 Messaging- Policies.

§18 Compression

Spec: Part 1 §18, S. 491 — Generic Compression Framework für GIOP-Payloads (Codec-Registrierung, Negotiation).

Repo: crates/corba-ccm/src/orb_extensions.rs::{CompressionAlgorithm, ZiopConfig} mit None/Zlib/Gzip/Lzma/Deflate-Algorithmen + ZiopConfig (algorithm/min_size_threshold/level).

Status: done — Compression-Framework + produktiver Codec via flate2 (Pure-Rust-Backend): CompressionAlgorithm::compress(input) und decompress(input) decken None (passthrough), Zlib (RFC 1950), Gzip (RFC 1952), Deflate (RFC 1951) ab. Lzma liefert CompressionError::Unsupported mit Decision-Record (xz2/liblzma- Build-Risiko unverhältnismäßig). 10-kB-Block-Test belegt das Roundtrip-Verhalten.

Part 2: Interoperability

§1, §3–§5 Scope/References/Terms/Symbols

Spec: Part 2 §1, §3–§5, S. 1-6 — Geltungsbereich, normative Referenzen, Begriffsdefinitionen, Symbole.

Repo: —

Tests: —

Status: n/a (informative) — Geltungsbereich, Verweislisten und Begriffe.

§2 Conformance and Compliance — Interoperabilität

Spec: Part 2 §2, S. 1 — “An ORB is considered to be interoperability-compliant when it meets the following requirements”: die APIs für Request-Level-Bridges (Dynamic Invocation Interface, Dynamic Skeleton Interface, die Objektidentitäts-Operationen) und IIOP (GIOP-Transfersyntax und Nachrichtenformate über TCP/IP). ZIOP ist ein optionaler Konformitätspunkt (Item §12).

Status: done

§2.1 MIOP — Erweiterung des Moduls IOP

Spec: Part 2 §2.1, S. 2 — const ProfileId TAG_UIPMC = 3; const ComponentId TAG_GROUP = 39; const ComponentId TAG_GROUP_IIOP = 40.

Repo: crates/corba-ior/src/profile_tags.rs (ProfileId::Uipmc), crates/corba-ior/src/component_tags.rs (ComponentId::Group, ComponentId::GroupIiop).

Tests: crates/corba-ior/src/profile_tags.rs::tests::standard_profile_tag_values_match_spec, crates/corba-ior/src/component_tags.rs::tests::round_trip_all_known_tags.

Status: done

§6 Interoperability Overview

Spec: Part 2 §6, S. 7 — Architektur-Überblick zur ORB-Interop.

Repo: —

Tests: —

Status: n/a (informative) — Überblick; die Anforderungen stehen in §7–§12.

§7.1–§7.5 Domains, ORB-Services, Bridging, Objektadressierung

Spec: Part 2 §7.1–§7.5, S. 15–24 — Domänen, ORB-Services, Bridging zwischen Domänen, Interoperabilitätsansätze, domänenrelative Objektreferenzen.

Repo: —

Tests: —

Status: n/a (informative) — Architekturbeschreibung; die erfüllbaren Aussagen von §7 stehen in §7.6–§7.10.

§7.6 Interoperable Object References (IOR)

Spec: Part 2 §7.6, S. 25–37 — IOR-Struktur, TaggedProfile, Standard-Profile, TaggedComponent, Standard-Komponenten, Zusammensetzung, stringifizierte IOR (IOR: + Hex der CDR-Encapsulation), Object URLs corbaloc (iiop, rir, Default-Port 2809, Default-Version 1.0, IPv6-Host in eckigen Klammern) und corbaname; fehlgeschlagene Umwandlung: BAD_PARAM mit Minor-Code 7 bis 10.

Status: partial — IOR, Profile, Komponenten, stringifizierte IOR und corbaloc/corbaname sind kodiert und getestet. Es fehlen: ein IPv6-Host ohne Port, rir zusammen mit einem anderen Protokoll und die Minor-Codes 7–10; eigenes Item.

§7.6.10 Object URLs — IPv6 ohne Port, `rir`-Ausschluss, Minor-Codes

Spec: Part 2 §7.6.10, S. 33–35 — <host> = DNS_style_host_name | IPv4_address | "[" IPv6_address "]", Port optional mit Default 2809; “The rir protocol cannot be used with any other protocol in a URL”; “If conversion fails, string_to_object raises a BAD_PARAM exception” mit Minor-Code 7 (bad scheme name), 8 (bad address), 9 (bad schema specific part), 10 (non-specific reason).

Repo: —

Tests: —

Status: open — parse_endpoint in crates/corba-ior/src/url.rs trennt den Port am letzten Doppelpunkt ab; ein IPv6-Host ohne Port (corbaloc::[::1]/key) wird dabei zerlegt und abgewiesen. Eine Liste mit rir und iiop wird angenommen. Fehler kommen als IorError, nicht als BAD_PARAM mit Minor-Code.

§7.7 Service Context

Spec: Part 2 §7.7, S. 37–40 — IOP::ServiceContext (context_id, context_data als CDR-Encapsulation), Standard-IDs (§7.7.1), Verarbeitungsregeln (§7.7.2): ein Kontext außerhalb der eigenen GIOP-Version oder außerhalb des OMG-Bereichs darf ignoriert werden, “must be passed on through a bridge and must be made available to interceptors. No exception shall be raised.”

Repo: crates/corba-giop/src/service_context.rs (ServiceContext, ServiceContextList, ServiceContextTag).

Status: partial — Kodierung der Liste und die Standard-IDs sind getestet; kein Test prüft die Verarbeitungsregeln §7.7.2 (unbekannte oder versionsfremde Kontexte ohne Exception weiterreichen und Interceptoren zugänglich machen).

§7.8 Coder/Decoder Interfaces

Spec: Part 2 §7.8, S. 40–43 — IOP::Codec (encode, decode, encode_value, decode_value) und IOP::CodecFactory::create_codec, erreichbar über resolve_initial_references("CodecFactory"); “The encodings which shall be supported are: ENCODING_CDR_ENCAPS, version 1.0; […] 1.1; […] 1.2”.

Repo: —

Tests: —

Status: open — kein Codec und keine CodecFactory im Baum.

§7.9 Feature Support and GIOP Versions

Spec: Part 2 §7.9, S. 43–44, Table 7.2 — welche Service-Kontexte, IOR-Komponenten und Funktionen ab welcher GIOP-Version 1.0 bis 1.4 gelten.

Status: partial — die Abhängigkeiten von GIOP 1.0 bis 1.2 sind umgesetzt und getestet; GIOP 1.3 und 1.4 fehlen, eigenes Item.

§7.9 GIOP 1.3 und 1.4

Spec: Part 2 §7.9, S. 43–44, Table 7.2 — Spalten V1.3 und V1.4.

Repo: —

Tests: —

Status: open — crates/corba-giop/src/version.rs kennt nur 1.0, 1.1 und 1.2.

§7.10 Code Set Conversion

Spec: Part 2 §7.10, S. 45–58 — Codeset-Komponente der IOR (TAG_CODE_SETS), Aushandlung des Übertragungs-Codesets für char und wchar, CodeSets-Service-Kontext, OSF-Registry-IDs, Umsetzung der Zeichendaten in das ausgehandelte Codeset.

Repo: crates/corba-ior/src/components.rs (CodeSetComponentInfo::negotiate), crates/corba-giop/src/code_set.rs (CodeSetContext).

Status: partial — Aushandlung, Service-Kontext und Registry-IDs sind getestet; die Umsetzung der Zeichendaten in ein ausgehandeltes Codeset außer UTF-8/UTF-16 fehlt, eigenes Item.

§7.10 Umsetzung in ein ausgehandeltes Codeset außer UTF-8/UTF-16

Spec: Part 2 §7.10.2, S. 48–55 — Client und Server setzen char- und wchar-Daten in das ausgehandelte Übertragungs-Codeset um (z. B. ISO 8859-1).

Repo: —

Tests: —

Status: open — crates/corba-giop/src/lib.rs beschreibt die ISO-Latin-Umsetzung als Aufgabe des Aufrufers; crates/wire/ kodiert nur UTF-8 und UTF-16.

§8 Building Inter-ORB Bridges

Spec: Part 2 §8, S. 63 — Inline-Bridges, Request-Level-Bridges.

Repo: —

Tests: —

Status: n/a (informative) — Part 2 §8.1: „an implementation-oriented conceptual framework for the construction of bridges“; die Klausel stellt keine Anforderung. Die CORBA↔︎DDS-Bridge steht in zerodds-corba-bridge-1.0.md.

§9 General Inter-ORB Protocol (GIOP)

Spec: Part 2 §9, S. 69 — GIOP Wire-Protokoll (alle 8 Message-Typen), CDR-Transfer-Syntax, Versionierung 1.0/1.1/1.2, IIOP-Mapping, Bi-Dir GIOP.

Repo: crates/corba-giop/src/ mit einer Datei je Message-Typ plus crates/corba-giop/src/header.rs, crates/corba-giop/src/codec.rs, crates/corba-giop/src/service_context.rs, crates/corba-giop/src/target_address.rs, crates/corba-giop/src/flags.rs, crates/corba-giop/src/version.rs.

Status: done

§9.3 CDR Transfer Syntax

Spec: §9.3, S. 71 — CDR-Encoding, Endianness-Markierung, Primitive/Konstrukt-Layout, GIOP 1.2 Alignment.

Repo: crates/wire/src/writer.rs + crates/wire/src/reader.rs (Primitive + Alignment + Encapsulation), Re-Use durch den GIOP-Codec in crates/corba-giop/src/codec.rs.

Status: done

§9.4 GIOP Message Formats

Spec: §9.4, S. 93 — alle 8 Message-Typen mit binärem Layout (Request/Reply/CancelRequest/LocateRequest/LocateReply/ CloseConnection/MessageError/Fragment).

Repo: Eine Datei pro Message-Typ in crates/corba-giop/src/ — crates/corba-giop/src/request.rs, crates/corba-giop/src/reply.rs, crates/corba-giop/src/cancel_request.rs, crates/corba-giop/src/locate_request.rs, crates/corba-giop/src/locate_reply.rs, crates/corba-giop/src/close_connection.rs, crates/corba-giop/src/message_error.rs, crates/corba-giop/src/fragment.rs.

Tests: Ein Oktett-Round-Trip je Message-Typ — crates/corba-giop/src/request.rs::{round_trip_giop_1_0_request, round_trip_giop_1_1_request_with_reserved_bytes, round_trip_giop_1_2_request_with_target_address}, crates/corba-giop/src/reply.rs::{round_trip_giop_1_0_no_exception, round_trip_giop_1_2_user_exception, round_trip_location_forward_perm_in_1_2}, crates/corba-giop/src/cancel_request.rs::tests::round_trip, crates/corba-giop/src/locate_request.rs::{round_trip_giop_1_0, round_trip_giop_1_2_with_profile_addr}, crates/corba-giop/src/locate_reply.rs::{round_trip_giop_1_0_object_here, round_trip_giop_1_2_object_forward_perm}, crates/corba-giop/src/fragment.rs::{round_trip_giop_1_2_with_header, round_trip_giop_1_1_without_header}. Alle acht über den Gesamt-Codec, CloseConnection und MessageError (ohne Body) nur dort: crates/corba-giop/src/codec.rs::{round_trip_request_giop_1_0_be, round_trip_close_connection, round_trip_message_error, round_trip_fragment_with_more_bit, round_trip_cancel_request, round_trip_locate_request_giop_1_2, round_trip_locate_reply_object_here}. Die Typ-Diskriminatoren selbst: crates/corba-giop/src/message_type.rs::tests::message_type_values_match_spec_table_15_1.

Status: done

§9.5 GIOP Message Transport

Spec: §9.5, S. 107 — Transport-Anforderungen (geordnet, ohne Verlust), Connection-Management.

Repo: crates/corba-iiop/src/connection.rs, crates/corba-iiop/src/acceptor.rs, crates/corba-iiop/src/connector.rs für TCP-Transport.

Tests: crates/corba-iiop/src/acceptor.rs::tests::round_trip_via_acceptor_and_connector, crates/corba-iiop/src/connection.rs::{round_trip_request_reply, shutdown_propagates_eof_to_peer, close_connection_message_round_trip}, crates/corba-iiop/src/framing.rs::tests::read_back_to_back_messages (Message-Grenzen im Strom), crates/corba-iiop/src/connector.rs::{connect_reuses_pooled_connection, invalidated_connection_is_not_returned_to_pool, max_connections_per_endpoint_is_enforced}.

Status: done — TCP via IIOP. Andere Transport-Bindings (z.B. SCTP) nicht angeboten.

§9.6 Object Location

Spec: §9.6, S. 110 — LocateRequest/LocateReply-Semantik, Forward- ing.

Repo: crates/corba-giop/src/locate_request.rs, crates/corba-giop/src/locate_reply.rs.

Spec: §10.2, S. 127 — SAS-Message-Codec (EstablishContext, CompleteEstablishContext, ContextError, MessageInContext).

Repo: crates/corba-csiv2/src/sas.rs (SasMessage mit encode_encapsulation/decode_encapsulation, IdentityToken).

Status: done

§10.3 Security Attribute Service (SAS)

Spec: §10.3, S. 137 — SAS-State-Machine, Stateful/Stateless Contexts.

Repo: crates/corba-csiv2/src/session.rs::{SasTarget, SasClient, TargetAction, RetainedContext, CONTEXT_ERROR_NO_CONTEXT, CONTEXT_ERROR_INVALID_EVIDENCE} — Target- und Client-Hälfte der State-Machine über den SasMessage-Typen aus §10.2; ein stateful Target hält den Kontext unter der ContextId und der Client schickt danach MessageInContext statt neuer Credentials, bis ein discard_context oder ein ContextError ihn zurück in den Establish-Zustand setzt.

Status: done — der letzte Test fährt die volle Sitzung über die §10.2-Oktette: jede Nachricht kreuzt encode_encapsulation / decode_encapsulation, bevor die Gegenseite sie sieht.

§10.4 Transport Security Mechanisms

Spec: §10.4, S. 149 — TLS/SSL-Bindings, Mutual-Auth.

Repo: TLS-Stack via crates/security-pki/ (X.509 + TLS). CSIv2-→-IIOP-TLS-Bind via crates/corba-csiv2::association_options + crates/corba-iiop-Acceptor (TAG_TLS_SEC_TRANS-Profile-Tags in crates/corba-ior/src/component_tags.rs); Glue ist im Acceptor-Lifecycle gebunden.

Status: done — TLS-Stack + CSIv2-IIOP-Bind via IOR-Tags live.

§10.5 Interoperable Object References (IOR mit Security-Tags)

Spec: §10.5, S. 150 — IOR-Format mit TAG_CSI_SEC_MECH_LIST, TAG_NULL_TAG, TAG_TLS_SEC_TRANS.

Repo: crates/corba-ior/src/component_tags.rs (ComponentId mit CsiSecMechList = 33, NullTag = 34, TlsSecTrans = 36), crates/corba-ior/src/components.rs (StructuredComponent), crates/corba-csiv2/src/mech_list.rs (CompoundSecMechList).

Tests: crates/corba-ior/src/ior.rs::tests::a_security_ior_carries_mech_list_tls_and_null_tag_through_a_round_trip — ein vollständiger IOR mit den drei Tags in der IIOP-Profile- Component-Liste, über encode_encapsulation/decode_encapsulation und zurück in die strukturierte Form. Tag-Werte und die Component-Bodies einzeln: crates/corba-ior/src/component_tags.rs::{well_known_component_tag_values_match_spec, round_trip_all_known_tags, at_least_32_well_known_tags_modelled}, crates/corba-ior/src/components.rs::{csi_sec_mech_list_round_trip, tls_sec_trans_with_addresses_round_trip, ssl_sec_trans_round_trip}.

Status: done

§10.6 Conformance Levels (CSIv2)

Spec: §10.6, S. 160 — vier CSIv2-Conformance-Level (0-3).

Repo: Implementierte Mechanismen in corba-csiv2 decken alle drei normativen Levels (0/1/2) ab; Conformance-Marker in crates/corba-ccm/src/lib.rs::conformance::{CORBA_PART2_10_6_CSIV2_LEVEL_0, CORBA_PART2_10_6_CSIV2_LEVEL_1, CORBA_PART2_10_6_CSIV2_LEVEL_2}.

Tests: conformance_tests::csiv2_level_markers_match_spec.

Status: done — Conformance-Marker für alle drei Levels explizit ausgewiesen.

§10.7 Sample Message Flows and Scenarios

Spec: §10.7, S. 162 — Beispiele.

Repo: —

Tests: —

Status: n/a (informative) — Beispielabläufe.

§10.8 References

Spec: §10.8, S. 171 — Referenzliste.

Repo: —

Tests: —

Status: n/a (informative) — Verweisliste.

§10.9 IDL für CSIv2

Spec: §10.9, S. 172 — IDL der CSI-Module.

Repo: als Rust-Repräsentation in crates/corba-csiv2/src/association_options.rs (AssociationOptions), crates/corba-csiv2/src/mech_list.rs (CompoundSecMechList, CompoundSecMech, AsContextSec, SasContextSec), crates/corba-csiv2/src/sas.rs (SasMsgType, IdentityToken, SASContextBody-Union als SasMessage), crates/corba-csiv2/src/gssup.rs (GssupCredentialToken).

Tests: Ein Wert-/Layout-Vergleich gegen die IDL je Modul — crates/corba-csiv2/src/association_options.rs::tests::flag_values_match_spec_table_24_1, crates/corba-csiv2/src/sas.rs::{sas_msg_type_values_match_spec, identity_token_discriminator_matches_spec}, crates/corba-csiv2/src/mech_list.rs::{cdr_roundtrip_compound_sec_mech_list, build_mech_list_with_tls_and_gssup, cdr_roundtrip_empty_list}, crates/corba-csiv2/src/gssup.rs::{initial_context_token_tag_is_0x60, gssup_oid_starts_with_der_tag, encapsulation_is_wire_correct_octet_seq_len_at_offset_4}.

Status: done

§11 Unreliable Multicast Inter-ORB Protocol (MIOP)

Spec: Part 2 §11, S. 181 — UDP-Multicast-Variante von GIOP für unreliable group communication.

Repo: crates/corba-ccm/src/orb_extensions.rs::{MiopConfig, MiopFrameHeader, MiopError, MulticastSink, MulticastSinkError, MiopSender, MIOP_MAGIC, MIOP_VERSION_1_0} mit IPv4-Multicast-Group + Port + TTL + Loopback-Flag (Default 239.255.0.1:5683 TTL=1) plus voller MIOP-Frame-Codec (16-Byte-Header inkl. MIOP-Magic-Bytes, Version 0x10, Flags-Endian/Last-Frag-Bit, Packet-Length, Unique-ID, Packet-Number, Number-of-Packets) und MiopSender::send_giop der GIOP-Bytes als Single-Packet bzw. Multi-Packet-Set über einen MulticastSink-Adapter versendet (Adapter-Trait, damit corba-ccm keinen transport-udp-Layer-Zyklus erzeugt).

Status: done — MIOP-Frame-Codec + Sender-Pfad mit Single-/ Multi-Packet-Fragmentierung + Multicast-Sink-Adapter-Trait..

§12 ZIOP Protocol

Spec: Part 2 §12, S. 219 — Zlib-/Compress-IOP-Messages, Compression-Policies.

Repo: crates/corba-ccm/src/orb_extensions.rs::ZiopConfig + CompressionAlgorithm (siehe §18 Compression).

Tests: crates/corba-ccm/src/orb_extensions.rs::tests::compression_algorithm_round_trip, ::compression_zlib_round_trip, ::compression_gzip_round_trip, ::compression_deflate_round_trip.

Status: done — ZIOP-Config-Daten-Modell + produktiver Compression- Codec (Cross-Ref §18 Compression). ZiopConfig.algorithm wählt aus den Backends (None/Zlib/Gzip/Deflate) den Codec; LZMA bleibt explizit unsupported.

Part 3: Component Model (CCM)

§1, §3–§5 Scope/References/Terms/Symbols

Spec: Part 3 §1, §3–§5, S. 1-7 — Geltungsbereich, Verweise, Begriffe, Symbole.

Repo: —

Tests: —

Status: n/a (informative) — Geltungsbereich, Verweislisten und Begriffe.

§2 Conformance and Compliance

Spec: Part 3 §2, S. 1–3 — Konformitätspunkte: Basic Level (für Nicht-Java-Produkte IDL-Erweiterungen, CIDL ohne Segmente, ein Container, XML-Deployment-Deskriptoren), Java-Basic-Level (EJB 1.1, RMI/IIOP, EJB-zu-IDL), Extended Level, Lightweight-CCM-Profil, EJB-Clients (optional), Generic Interaction Support (porttype, mirrorport, port, Templates, Connectoren, D&C-Erweiterungen).

Repo: crates/corba-ccm/src/container.rs, crates/corba-ccm/src/cidl.rs, crates/corba-ccm-ejb/, crates/corba-ccm-lib/.

Tests: crates/corba-ccm/src/container.rs::tests::install_and_full_lifecycle_round_trip.

Status: partial — Container, Komponentenmodell, EJB-Integration und Lightweight-Profil sind als Items §6–§17 geführt; dem Basic Level fehlt der CIDL-Parser (Item „§8 OMG CIDL — verbleibende Konstrukte“, open).

§6 Component Model

Spec: Part 3 §6, S. 9 — Component-Definition, Facets, Receptacles, Events, Homes, Home-Finders, Configuration, Inheritance, Conformance.

Repo: crates/corba-ccm/src/component_def.rs, crates/corba-ccm/src/home.rs, crates/corba-ccm/src/port.rs, crates/corba-ccm/src/context.rs, crates/corba-ccm/src/lifecycle.rs.

Tests: crates/corba-ccm/src/component_def.rs::tests (30 Tests), darunter trader_has_4_ports, keyed_component_detected, provide_facet_returns_facet_by_name, get_all_facets_returns_complete_list, get_all_publishers_excludes_emit_only_sources, supports_interface_returns_true_for_listed_iface, the_base_chain_runs_from_the_derived_component_to_the_root, flattening_takes_over_every_inherited_feature_bases_first, a_redefined_port_name_is_refused_rather_than_shadowed, a_second_primary_key_in_the_chain_is_refused; crates/corba-ccm/src/cidl.rs::tests::all_four_composition_categories_distinct; die Unter-Items §6.5-§6.13 nennen je einen Test pro Klausel.

Status: done

Spec: §6.13, S. 51 — Conformance-Punkte für CCM-Compliance.

Repo: Conformance-Marker in crates/corba-ccm/src/lib.rs::conformance::CORBA_PART3_6_13_CCM_CONFORMANCE + Cross-Ref §14 Lightweight CCM Profile-Marker.

Tests: conformance_tests::corba_part3_6_13_marker_namespace.

Status: done — Conformance-Marker als Doc-Constant ausgewiesen.

§7 Generic Interaction Support (IDL3+)

Spec: Part 3 §7, S. 55 — Connector-Modell, IDL3+-Templates, Generic Interaction Patterns.

Repo: Simple Connectors via crates/corba-ccm/src/port.rs + crates/corba-ccm-lib/src/dds_bridge.rs. IDL3+-Templates als Codegen-Erweiterung sind Caller-Layer (echtes IDL3+-Template-System ist eine separate Spec-Schicht; Spec §7.3/§7.4 erlaubt explizit “basic Connectors only” als minimalen Conformance-Pfad). Conformance-Marker corba-ccm::conformance:: CORBA_PART3_7_GENERIC_INTERACTION.

Tests: Inline + conformance_tests::corba_part3_7_marker_namespace.

Status: done — Simple Connectors als Spec-konforme Mindest- Conformance live; IDL3+-Templates bleiben optional.

§8 OMG CIDL Syntax and Semantics

Spec: Part 3 §8, S. 81 — Component Implementation Definition Language (Composition, Home/Segment Executor, Persistence, Facet/Feature Delegation, Proxy Home).

Repo: crates/corba-ccm/src/cidl.rs::{Composition, CompositionCategory, HomeExecutor, StorageType, StorageHome} — Datenmodell der CIDL-Konstrukte plus die Kategorie-Regel (entity verlangt eine Storage-Home, die übrigen drei nicht).

Status: partial — Composition, Home-Executor und die Persistence- Konstrukte (storagetype/storagehome) sind als AST vorhanden und über die Kategorie-Regel geprüft. Es fehlen: ein CIDL-Parser (das Modul sagt selbst, die Sprache sei Caller-Layer), die Segment-Definition (segment-Executor je Facet-Gruppe), die Facet-/Feature-Delegation (delegatesto/abstract storagehome) und der Proxy Home. Der Rest steht als eigenes Item in corba-3.3.open.md.

§8 OMG CIDL — verbleibende Konstrukte

Spec: Part 3 §8, S. 81 — die CIDL-Grammatik selbst, die segment-Definition (ein Executor je Facet-Gruppe statt einer je Komponente), die Facet-/Feature-Delegation (delegatesto, abstract storagehome) und der Proxy Home.

Repo: —

Tests: —

Status: open — im Baum existiert nur das Datenmodell aus §8 oben. Es gibt keinen Lexer/Parser für CIDL-Quelltext (das Modul crates/corba-ccm/src/cidl.rs sagt selbst, die Sprache sei Caller-Layer), keinen Segment-Typ, keine Delegations-Klausel und keinen Proxy Home. Plan: die CIDL-Produktionen an den bestehenden IDL-Frontend (crates/idl-cst + crates/idl-parse) anhängen und die vier Konstrukte als AST-Knoten ergänzen; das Datenmodell aus §8 ist das Ziel des Lowerings.

§9 CCM Implementation Framework (CIF)

Spec: Part 3 §9, S. 93 — CIF-Architektur, Sprach-Mapping zu C++.

Tests: crates/corba-ccm/src/cif.rs::{lifecycle_calls_increment_counters, cif_error_carries_diagnostic} (Executor-Lifecycle ccm_activate/ccm_passivate/ccm_remove), crates/corba-codegen/src/skeleton.rs::{cpp_compares_with_strcmp_and_ends_in_bad_operation, every_operation_reaches_the_dispatch_in_every_column} und crates/corba-codegen/src/stub.rs::{a_variable_length_struct_returns_a_pointer_and_a_fixed_one_a_value, an_object_reference_argument_is_a_ptr_and_its_out_is_an_out} für das C++-Sprach-Mapping.

Status: done

§16 Deployment IDL for CCM

Spec: Part 3 §16, S. 329 — D&C-IDL.

Repo: als Rust-Repräsentation in crates/corba-dnc/src/plan.rs (DeploymentPlan, InstanceDeploymentDescription, PlanConnection), crates/corba-dnc/src/repository.rs (RepositoryManager, PackageConfiguration), crates/corba-dnc/src/node.rs (NodeManager, NodeApplication, NodeApplicationManager), crates/corba-dnc/src/execution.rs (ExecutionManager, DomainApplicationManager).

Tests: Ein Test je IDL-Interface-Operation-Gruppe — crates/corba-dnc/src/plan.rs::{valid_plan_passes_validation, instance_with_unknown_impl_fails, connection_with_unknown_instance_fails, co_location_with_unknown_instance_fails}, crates/corba-dnc/src/repository.rs::{install_and_find_round_trip, list_packages_returns_all_labels, delete_existing_returns_true, delete_unknown_returns_false, install_overwrites_duplicate}, crates/corba-dnc/src/node.rs::{prepare_plan_then_start_launch, destroy_application_clears_active, register_and_unregister_application, unregister_unknown_returns_none}, crates/corba-dnc/src/execution.rs::tests::execution_manager_lists_prepared_plans.

Status: done

§17 XML Schema for CCM

Spec: Part 3 §17, S. 343 — XML-Schema für Deployment-Pläne.

Repo: crates/corba-dnc/src/xml.rs.

Tests: crates/corba-dnc/src/xml.rs::{parses_minimal_plan, parses_multiple_artifacts, validation_fails_on_unknown_impl_reference, missing_root_tag_returns_expected_tag, co_locate_with_parsed}.

Status: done

Beigeordnete OMG-Service: COS Naming v1.3 (formal/04-10-03)

CosNaming-Service ist eigene Spec, wird hier als Initial-Reference gemäß Part 1 §8.5.2 mitgeführt.

CosNaming::NamingContext

Spec: CosNaming v1.3 §2 — bind/rebind/unbind/resolve/ new_context, Iterator-basiertes list(), stringified Names ("a/b/c"-Pattern via NamingContextExt::resolve_str).

Repo: crates/corba-cosnaming/src/context.rs, crates/corba-cosnaming/src/name.rs, crates/corba-cosnaming/src/stringified.rs.

Tests: crates/corba-cosnaming/src/context.rs::tests (13 Tests): bind_and_resolve_simple, double_bind_yields_already_bound, rebind_replaces_existing, nested_context_resolve, resolve_to_context_returns_context, resolve_unknown_yields_missing_node, unbind_removes_entry, destroy_with_bindings_yields_not_empty, destroy_empty_is_ok, list_returns_all_bindings_with_correct_type, resolve_str_via_naming_context_ext, to_url_constructs_corbaname, empty_name_is_invalid; crates/corba-cosnaming/src/stringified.rs::tests (9), crates/corba-cosnaming/src/name.rs::tests (3).

Status: done

ZeroDDS-spezifische Bridges (kein OMG-Item)

CORBA-Object ↔︎ DDS-Topic Bridge

Spec: kein OMG-Spec-Item; ZeroDDS-spezifische Migrations-Schicht zur schrittweisen Ablösung von CORBA-Endpoints durch DDS-Wire.

Repo: crates/corba-dds-bridge/src/mapping.rs (IOR↔︎Topic+Instance), crates/corba-dds-bridge/src/servant.rs (CORBA-Servant über DDS-RPC), crates/corba-dds-bridge/src/sync.rs.

Tests: crates/corba-dds-bridge/src/mapping.rs::tests (6 Tests): add_and_lookup_route, lookup_unknown_yields_none, operation_mapping_by_name, add_route_replaces_existing, all_routes_listing, direction_variants_distinct; crates/corba-dds-bridge/src/locate.rs::tests (4), crates/corba-dds-bridge/src/notify.rs::tests (4), crates/corba-dds-bridge/src/csiv2_wire.rs::tests (4), crates/corba-dds-bridge/src/bridge_security.rs::tests (5).

Status: done — informativ; nicht spec-pflichtig.

Audit-Status

51 done / 6 partial / 6 open / 0 blocked / 12 n/a (informative).

Test-Lauf:

cargo test -p zerodds-corba-giop --lib — 80 Tests grün.
cargo test -p zerodds-corba-iiop --lib — 38 Tests grün.
cargo test -p zerodds-corba-ior --lib — 53 Tests grün.
cargo test -p zerodds-corba-poa --lib — 39 Tests grün.
cargo test -p zerodds-corba-cosnaming --lib — 25 Tests grün.
cargo test -p zerodds-corba-csiv2 --lib — 35 Tests grün.
cargo test -p zerodds-corba-cos-event --lib — 23 Tests grün.
cargo test -p zerodds-corba-ccm --lib — 181 Tests grün.
cargo test -p zerodds-corba-ccm-lib --lib — 23 Tests grün.
cargo test -p zerodds-corba-ccm-ejb --lib — 25 Tests grün.
cargo test -p zerodds-corba-ir --lib — 23 Tests grün.
cargo test -p zerodds-corba-dnc --lib — 30 Tests grün.
cargo test -p zerodds-corba-dds-bridge --lib — 43 Tests grün.
cargo test -p zerodds-corba-codegen --tests — 38 + 15 + 10 Tests grün.
cargo test -p zerodds-idl-parse --tests — 36 + 32 Tests grün.
cargo test -p zerodds-idl-lower --tests — 5 + 49 + 23 + 12 + 36 + 4 + 82 + 3 + 62 Tests grün.

Offene Punkte: corba-3.3.open.md.

OMG CORBA 3.3 — Spec Coverage (WP CORBA Coexistence)

Part 1: Interfaces

§1 Scope

§2 Conformance and Compliance

§3 Normative References

§4 Additional Information

§5 The Object Model

§6 CORBA Overview

§7 IDL Syntax and Semantics

§8 ORB Interface

§9 Value Type Semantics

§10 Abstract Interface Semantics

§11 Dynamic Invocation Interface (DII)

§12 Dynamic Skeleton Interface (DSI)

§13 Dynamic Management of Any Values (DynAny)

§14 The Interface Repository

§15 The Portable Object Adapter (POA)

§16 Portable Interceptors

§17 CORBA Messaging

§18 Compression

Part 2: Interoperability

§1, §3–§5 Scope/References/Terms/Symbols

§2 Conformance and Compliance — interoperability

§2.1 MIOP — extension of the IOP module

§6 Interoperability Overview

§7.1–§7.5 Domains, ORB services, bridging, object addressing

§7.6 Interoperable Object References (IOR)

§7.6.10 Object URLs — IPv6 without port, rir exclusion, minor codes

§7.7 Service Context

§7.8 Coder/Decoder Interfaces

§7.9 Feature Support and GIOP Versions

§7.9 GIOP 1.3 and 1.4

§7.10 Code Set Conversion

§7.10 Conversion into a negotiated code set other than UTF-8/UTF-16

§8 Building Inter-ORB Bridges

§9 General Inter-ORB Protocol (GIOP)

§9.3 CDR Transfer Syntax

§9.4 GIOP Message Formats

§9.5 GIOP Message Transport

§9.6 Object Location

§9.7 Internet Inter-ORB Protocol (IIOP)

§9.8/§9.9 Bi-Directional GIOP

§9.10 OMG IDL for GIOP

§10 Secure Interoperability (CSIv2)

§10.2 Protocol Message Definitions

§10.3 Security Attribute Service (SAS)

§10.4 Transport Security Mechanisms

§10.5 Interoperable Object References (IOR with security tags)

§10.6 Conformance Levels (CSIv2)

§10.7 Sample Message Flows and Scenarios

§10.8 References

§10.9 IDL for CSIv2

§11 Unreliable Multicast Inter-ORB Protocol (MIOP)

§12 ZIOP Protocol

Part 3: Component Model (CCM)

§1, §3–§5 Scope/References/Terms/Symbols

§2 Conformance and Compliance

§6 Component Model

§6.5 Facets and Navigation

§6.6 Receptacles

§6.7 Events

§6.8 Homes / §6.9 Home Finders

§6.10 Component Configuration / §6.11 Attributes

§6.12 Component Inheritance

§6.13 Conformance Requirements

§7 Generic Interaction Support (IDL3+)

§8 OMG CIDL Syntax and Semantics

§8 OMG CIDL — Remaining Constructs

§9 CCM Implementation Framework (CIF)

§10 The Container Programming Model

§11 Integrating with Enterprise JavaBeans (EJB)

§12 Interface Repository Metamodel

§13 CIF Metamodel

§14 Lightweight CCM Profile

§15 Deployment PSM for CCM

§16 Deployment IDL for CCM

§17 XML Schema for CCM

Adjacent OMG service: COS Naming v1.3 (formal/04-10-03)

CosNaming::NamingContext

ZeroDDS-specific bridges (no OMG item)

§7.6.10 Object URLs — IPv6 without port, `rir` exclusion, minor codes

§7.6.10 Object URLs — IPv6 ohne Port, `rir`-Ausschluss, Minor-Codes