Legacy Issue Number: 4128
Source: Progress Software ( Eoghan Glynn)
There appears to be a contradiction in CORBA 2.4.1 (00-11-07) as to
whether CORBA::ORB::object_to_string() should raise INV_OBJREF or
BAD_PARAM when an invalid string is passed.
Here's where I see a contradiction in the spec:
CORBA 2.4.1: "18.104.22.168 INV_OBJREF
This exception indicates that an object reference is internally
malformed. For example, the repository ID may have incorrect syntax or
the addressing information may be invalid. This exception is raised by
ORB::string_to_object if the passed string does not decode correctly."
This explicitly specifies that INV_OBJREF is thrown if a non-decodable
stringified IOR is passed to string_to_object().
On the other hand the table:
CORBA 2.4.1: "4.11.4 Standard Minor Exception Codes ...
7 string_to_object conversion failed due to bad scheme name.
8 string_to_object conversion failed due to bad address.
9 string_to_object conversion failed due to bad bad schema specific
10 string_to_object conversion failed due to non specific reason."
indicates that BAD_PARAM/10 should be raised for non-specific
string_to_object failures, contradicting 22.214.171.124 above.
Is this simply an editing issue in that 126.96.36.199 has not yet been
updated to take cognizance of 4.11.4? I propose that 188.8.131.52 is updated
to allow BAD_PARAM to be raised on string_to_object failures where the
problem lies in the string content.
Reported: CORBA 2.4.1 — Tue, 19 Dec 2000 05:00 GMT
Disposition: Resolved — CORBA 2.5
see above, Close issue, already fixed
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA25 — CORBA::ORB::object_to_string() raising INV_OBJREF or BAD_PARAM
- Key: CORBA25-6
- OMG Task Force: Core December 2000 RTF