Legacy Issue Number: 5689
Source: Floorboard Software ( Jonathan Biggar)
It is undocumented what should happen if an exception is thrown while
the ORB initialization process is calling ORBInitializer::pre_init or
In section 220.127.116.11 concerning the Java binding, the following statement
related to calling pre_init and post_init appears:
"If there are any exceptions, the ORB shall ignore them and proceed."
Taking this as precedent, it suggests that exceptions raised by pre_init
and post_init should be ignored. However, I'm not convinced that this
is a good idea, since a failure in an ORBInitializer is very likely to
cause the application to fail in mysterious ways later on that would be
difficult to debug.
I think it would be better to define explicit behavior for exceptions
raised from pre_init and post_init to be that the ORB initialization is
abandoned and the ORB is destroyed. Any ORBInitializer implementation
that really needs the ORB to ignore any thrown exceptions can simply
catch and discard them itself.
Reported: CORBA 3.0 — Wed, 16 Oct 2002 04:00 GMT
Disposition: Resolved — CORBA 3.0.2
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA3 — Exception handling in Interceptor initialization
- Key: CORBA3-90
- OMG Task Force: Core 2002 RTF