Common Object Request Broker Architecture Avatar
  1. OMG Specification

Common Object Request Broker Architecture — Open Issues

  • Acronym: CORBA
  • Issues Count: 7
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Add optional/map mapping (and other IDL4 special types)

  • Status: open   Implementation work Blocked
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    For IDl4 the CDR marshaling should be described, optional could be described as a union with a boolean discriminant, with TRUE containing the value, map as a sequence of structs containing each key/value, other IDL4 extensions can also be described using IDL base types marshaling. That also enables interoperability of optional/map/others with an old implementation without IDL4 support, the IDL has to be rewritten to work, but at that moment an IDL3 app can talk with a IDL4 app (at least for CDR)

  • Reported: CORBA 3.4 — Mon, 27 May 2024 06:22 GMT
  • Updated: Thu, 12 Sep 2024 21:22 GMT

The CCM document component-formal-21-02-04 shall be removed from CORBA 3.4 to become a standalone CCM specification.

  • Status: open  
  • Source: Objective Interface Systems ( Mr. Chuck Abbott)
  • Summary:

    The component-formal-21-02-04 for CORBA 3.4 part 3 will be moved to its own separate specification.

  • Reported: CORBA 3.4 — Thu, 28 Mar 2024 17:17 GMT
  • Updated: Wed, 12 Jun 2024 20:43 GMT

Add support for IDL4 int8/uint8/map/bitset/bitfield/bitmask

  • Status: open   Implementation work Blocked
  • Source: Remedy IT Expertise BV ( Johnny Willemsen)
  • Summary:

    CORBA 3.4 should have support for int8/uint8/map/bitset/bitfield/bitmask/bitvalue for DynamicAny, DynamicSkeleton, Interface Repo, Any/TypeCode and other CORBA APIs related to types

  • Reported: CORBA 3.4 — Mon, 17 Jul 2023 13:56 GMT
  • Updated: Wed, 6 Dec 2023 23:16 GMT


Extend InvalidName exception

  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    We propose to extend the InvalidName exception with a "string name" member to simplify analyzing problems when this exception is thrown, the exception will tell at that moment the name that failed

  • Reported: CORBA 3.4 — Mon, 11 Oct 2021 08:56 GMT
  • Updated: Wed, 6 Dec 2023 22:10 GMT

Replace Cookie with a string and use IDL map

  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    Currently CCM uses a Cookie which is returned from the connect operations which has to be pased with disconnect. This requires the deployment tooling to store this Cookie at deployment for usage later on at teardown. As each connection has a unique string id in the plan we propose to replace the Cookie with the unique string id which is from the deployment plan. With a connect this string is passed with the connect call, later on with disconnect the same string can be passed again. For all calls that retrieve a struct containing a Cookie we propose to replace this with a IDL map with the string as id , the reference as second value.

    These changes make deployment logic/tooling much easier, also now a IDL map is used which makes user code more clean instead of emulating a map with a sequence with a struct where the user has to search themselves.

  • Reported: CORBA 3.4 — Fri, 20 Aug 2021 09:23 GMT
  • Updated: Wed, 6 Dec 2023 22:10 GMT

ConfigValues to a std map

  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    It would be a much easier API for the user when ConfigValues would be a IDL map of FeatureName and a any

  • Reported: CORBA 3.4 — Wed, 16 Aug 2023 07:27 GMT
  • Updated: Wed, 6 Dec 2023 22:06 GMT