Legacy Issue Number: 3459
Source: Floorboard Software ( Jonathan Biggar)
The CORBA 2.3.1 specification does not cover the interaction between the
DynValue interface and custom valuetypes.
I frankly don't see any way that the DynValue interface can possibly
correctly handle a custom valuetype when the ORB does not have a factory
for the type. It is theoretically possible for DynValue to properly
work with a known custom type, but the implementation strategy could not
be based on parsing the marshalled form of the valuetype.
So, there are two issues that need to be addressed:
1. Should DynValue handle custom valuetypes at all?
2. For the set of custom valuetypes that it cannot handle, what
exceptions should be raised by each operations?
Reported: CORBA 2.3.1 — Sat, 25 Mar 2000 05:00 GMT
Disposition: Deferred — CORBA 3.4
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
Updated: Mon, 30 Mar 2020 19:47 GMT