-
Key: CORBA25-27
-
Legacy Issue Number: 4285
-
Status: closed
-
Source: Oracle ( Harold Carr)
-
Summary:
"This indicates that an object reference denotes an existing object,
but that the object does not support the operation that was invoked."This text does not specify a minor code nor a completion status.
Section 11.3.4.1 (last paragraph) says:
"If the ServantManager returns the wrong type of Servant, it is
indeterminate when that error is detected. It is likely to result in a
BAD_OPERATION with standard minor code 5 or MARSHAL exception at the
time of method invocation."This implies that 4.11.3.13 should specify a '5' for the minor code.
A specific minor code for this case is necessary since BAD_OPERATION
may be raised in other contexts (e.g., IDL->Java mapping for union,
Any, any extraction, ...).I am not sure why it says '5' in 4.11.3.13. Is this minor code
specified somewhere else that I'm missing?Assuming that this is underspecified I would suggest:
1. assigning a minor code for the case discussed in 4.11.3.13,
2. making sure that 11.3.4.1 is in sync with that assignment,
3. specifying a completion status of COMPLETED_NO (since there is no
way anything could be completed since the call never makes it out of
the skeleton into the servant). -
Reported: CORBA 2.4.2 — Thu, 26 Apr 2001 04:00 GMT
-
Disposition: Resolved — CORBA 2.5
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA25 — BAD_OPERATION needs minor code and completion status
- Key: CORBA25-27
- OMG Task Force: Core December 2000 RTF