CORBA25 — Ambiguity in non_existent

Section 4.3.5.1 non_existent last paragraph says:

Probing for object non-existence may require contacting the ORB that
implements the
target object. Such an attempt may fail at either the local or the
remote end. If non-existent
cannot make a reliable determination of object existence due to failure,
it
raises an exception in the calling application code. This enables the
application to
distinguish among the true, false, and indeterminate cases.

This does not define what exception gets thrown in the indeterminate
case. I picked TRANSIENT, but COMM_FAILURE or NO_RESPONSE may also be
valid choices.

Proposal:

Change the sentence in last paragraph of section 4.3.5.1:
If non-existent cannot make a reliable determination of object existence
due to failure, it
raises an exception in the calling application code.

to:
If non-existent cannot make a reliable determination of object existence
due to failure, it
raises a TRANSIENT with XX minor code in the calling application code.

close, no change