Legacy Issue Number: 5691
Source: Floorboard Software ( Jonathan Biggar)
There is no information in chapter 21 that specifies which operations on
ORBInitInfo can be legally called during pre_init or post_init.
The intention appears to be that calls to register new interceptors or
allocate a new slot id should be illegal during post_init.
Calling resolve_initial_references during pre_init does not appear to be
wise, but otherwise seems benign.
Add the following to 188.8.131.52:
"During a call to post_init(), invoking the ORBInitInfo methods:
allocate_slot_id or add_ior_interceptor will raise the BAD_INV_ORDER
standard system exception with minor code nnn."
Reported: CORBA 3.0 — Fri, 18 Oct 2002 04:00 GMT
Disposition: Resolved — CORBA 3.0.2
Fix it as suggested in the archive.
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA3 — What ORBInitInfo operations are legal during pre_init() and post_init()?
- Key: CORBA3-92
- OMG Task Force: Core 2002 RTF