-
Key: CORBA25-3
-
Legacy Issue Number: 4034
-
Status: closed
-
Source: Borland Software Corporation ( Vijaykumar Natarajan)
-
Summary:
Section 11.3.2.6 has a paragraph that states:
If the ORB::shutdown operation is called, it makes a call on deactivate
with a
TRUE etherealize_objects parameter for each POA manager known in the
process;
the wait_for_completion parameter to deactivate will be the same as the
similarly
named parameter of ORB::shutdown.Shouldn't this be reworded to not require an explicit call to
deactivate(but only the effect). Also, since ORB::shutdown already does
the equivalent of destroy on the POAs shouldn't the order of these
operations be specified. I also think they should be specified in the
text for ORB shutdown rather than here. -
Reported: CORBA 2.4.1 — Wed, 8 Nov 2000 05:00 GMT
-
Disposition: Resolved — CORBA 2.5
-
Disposition Summary:
Right, make it so
-
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA25 — POAManager::deactivate should not mandate ORB::shutdown implementation
- Key: CORBA25-3
- OMG Task Force: Core December 2000 RTF