Previous | Table of Contents | Next |
The association of service contexts with GIOP versions, (along with some other
supported features tied to GIOP minor version), is shown in Table 13-2..
Table 13-2 Feature Support Tied to Minor GIOP Version Number
Feature |
Version 1.0 |
Version 1.1 |
Version 1.2 |
Version 1.3 |
|
TransactionService Service Context | yes | yes | yes | yes | |
CodeSets Service Context | yes | yes | yes | ||
DCOM Bridging Service Contexts: ChainBypassCheck ChainBypassInfo LogicalThreadId | yes | yes | |||
Object by Value Service Context: SendingContextRunTime | yes | yes | |||
Bi-Directional IIOP Service Context: BI_DIR_IIOP | yes | yes | |||
Asynch Messaging Service Context INVOCATION_POLICIES | optional$ | yes | |||
Firewall Service Context FORWARDED_IDENTITY | optional$ | yes | |||
Java Language Throwable Service Context: UnknownExceptionInfo | yes | yes | |||
Realtime CORBA Service Contexts RTCorbaPriority RTCorbaPriorityRange | optional (Realtime CORBA only) | optional (Realtime CORBA only) |
Table 13-2 Feature Support Tied to Minor GIOP Version Number (Continued) Table 13-2 Feature Support Tied to Minor GIOP Version
Number (Continued)
Feature |
Version 1.0 |
Version 1.1 |
Version 1.2 |
Version 1.3 |
|
ExceptionDetailMessage Service Context | optional | yes | |||
FT_GROUP_VERSION | optional$$ | yes | |||
FT_REQUEST | optional$$ | yes | |||
SecurityAttributeService | optional$$ | yes | |||
ActivityService | optional$$ | yes | |||
IOR components in IIOP profile | yes | yes | yes | ||
TAG_ORB_TYPE | yes | yes | yes | ||
TAG_CODE_SETS | yes | yes | yes | ||
TAG_ALTERNATE_IIOP_ADDRESS | yes | yes | |||
TAG_ASSOCIATION_OPTION | yes | yes | yes | ||
TAG_SEC_NAME | yes | yes | yes | ||
TAG_SSL_SEC_TRANS | yes | yes | yes | ||
TAG_GENERIC_SEC_MECH | yes | yes | yes | ||
TAG_*_SEC_MECH | yes | yes | yes | ||
TAG_JAVA_CODEBASE | yes | yes | |||
TAG_FIREWALL_TRANS | optional$ | yes | |||
TAG_SCCP_CONTACT_INFO | optional$ | yes | |||
TAG_TRANSACTION_POLICY | optional$ | yes | |||
TAG_MESSAGE_ROUTERS | optional$ | yes | |||
TAG_OTS_POLICY | optional$ | yes | |||
TAG_INV_POLICY | optional$ | yes | |||
TAG_INET_SEC_TRANS | optional$ | yes | |||
Extended IDL data types | yes | yes | yes | ||
Bi-Directional GIOP Features | yes | yes | |||
Value types and Abstract Interfaces | yes | yes | |||
TAG_CSI_SEC_MECH_LIST | optional$$ | yes | |||
TAG_NULL_TAG | optional$$ | yes | |||
TAG_SECIOP_SEC_TRANS | optional$$ | yes | |||
TAG_TLS_SEC_TRANS | optional$$ | yes | |||
TAG_ACTIVITY_POLICY | optional$$ | yes |
Feature |
Version 1.0 |
Version 1.1 |
Version 1.2 |
Version 1.3 |
|
_component | yes | ||||
tk_abstract_interface tk_local_interfacel | optional$$ | yes | |||
tk_component tk_home tk_event | yes |
Note – $, $$All features that have been added after CORBA 2.3 have been marked as optional in GIOP 1.2. These features cannot
be compulsory in GIOP 1.2 since there is no way to incorporate them in deployed implementations of 1.2. However, in order
to have the additional features of CORBA 2.4 work properly these optional features must be supported by the GIOP 1.2 implementation
connecting CORBA 2.4$ or CORBA 2.5 or 2.6$$ ORBs.