CORBA25 — Minor code 2 description for OBJECT_NOT_EXIST not consistent w/ use

I was looking at the spec to amend 4033 to not use up a new minor code but
noticed this text for minor code 2 under OBJECT_NOT_EXIST:

POAManager::incarnate failed to create POA.

This is clearly not consistent with its use under the TRANSIENT POA Lifespan
Policy description (I also found other inconsistent uses, detailed below).

There are two things that need fixing here. The first one is probably
straightforward.
1. The minor code allocated for 4033 must be used in the text for TRANSIENT
Lifespan Policy in section 11.3.7.2

2. POAManager::incarnate is not a valid operation at all.
I found references to OBJECT_NOT_EXIST with minor code 2 in the following
places:

A - Section 11.2.6, paragraph 2

The adapter activator has the opportunity to create the required POA. If it
does not, the client receives the
OBJECT_NOT_EXIST exception with standard minor code 2.

B - Section 11.2.6
If the POA has the NON_RETAIN policy or has the RETAIN policy but didn't
find a
servant in the Active Object Map, the POA takes the following actions:
Bullet 3

• If t he USE_OBJECT_MAP_ONLY policy is in effect, the POA raises the
  OBJECT_NOT_EXIST system exception with standard minor code 2.

C - 11.3.3.2 unknown_adapter
If the operation returns TRUE, the ORB will
proceed with processing the request. If the operation returns FALSE, the ORB
will
return OBJECT_NOT_EXIST with standard minor code 2 to the client.

D - 11.3.3.2 unknown_adapter
If the parent of a nonexistent POA does not have an
associated adapter activator, the ORB will return the OBJECT_NOT_EXIST
system
exception with standard minor code 2.

E - 11.3.7.6 Request Processing Policy
USE_ACTIVE_OBJECT_MAP_ONLY - If the Object Id is not found in the
Active Object Map, an OBJECT_NOT_EXIST system exception with standard
minor code 2 is returned to the client.

Cases A, C and D hint that minor code 2 should actually say "Could not
create or locate POA" or something to that effect. Cases B and E should
really be using another minor code ("Could not locate object in AOM?").

incorporate change and close issue