Expand description
Runtime types that the generated code references.
Phase 1 skeleton. The full wire implementation (GIOP marshalling +
IIOP connection) follows in phase 2 via corba-iiop and
corba-giop. Here live only the public API structures that the
emitted stub/skeleton/valuetype references.
Structs§
- Object
Reference - CORBA object reference (IOR-encoded). Generated stubs hold an instance of this struct as a connection handle.
- PoaBuilder
- CORBA POA builder for server-side object activation.
- Type
Code - CORBA
TypeCode— type-reflection wrapper. - Value
Stream Reader - Stream API for reading valuetype wire bytes (CDR §15.3.4).
- Value
Stream Writer - Stream API for ValueBase wire marshalling (CDR §15.3.4).
Enums§
- Corba
Exception - CORBA system/user exception. Generated stubs/skeletons map all error paths onto this variant.
- IdAssignment
Policy - POA IdAssignment policy (§11.3.6).
- IdUniqueness
Policy - POA IdUniqueness policy (§11.3.7).
- Implicit
Activation Policy - POA ImplicitActivation policy (§11.3.8).
- Lifespan
Policy - POA lifespan policy (Spec §11.3.5).
- Request
Processing Policy - POA RequestProcessing policy (§11.3.10).
- Servant
Retention Policy - POA ServantRetention policy (§11.3.9).
- Skeleton
Result - Result of a skeleton dispatch.
- Thread
Policy - POA threading policy (Spec §11.3.4).
- Value
TagHeader - Spec §15.3.4.2 — header variant of a value-tag.
Traits§
- Async
Corba Channel - Abstract asynchronous GIOP channel to ONE target object (CORBA Messaging
§22) used by the generated AMI stubs (
sendc_/sendp_). Implemented by the transport layer (zerodds-corba-interop::AmiClient) — same layering pattern asCorbaConnectionfor the synchronous side. - Component
Home - CCM home trait. End-user homes implement this plus the specific
create()operation. - Component
Servant - CCM container servant marker. Concrete component implementations
implement this plus the
ComponentHometrait. - Corba
Connection - Connection handle used by stubs to send GIOP requests.
Phase 1 is an adapter trait whose full implementation lives in
corba-iiop. - Servant
- POA servant marker. Concrete server implementations implement this plus the respective IDL interface trait.
- Value
Base - ValueBase trait. All IDL valuetypes extend this.
Type Aliases§
- Async
Reply - Reply outcome of an asynchronous invocation (CORBA Messaging §22): the raw reply body + its on-wire byte order on success, otherwise the CORBA exception.
- Async
Reply Callback - Callback for the AMI callback model (§22.5) — invoked exactly once.