CORBA3 — Codeset negotiation and the CODESET_INCOMPATIBLE exception

1. There's no minor code assigned to the use of CODESET_INCOMPATIBLE
for a failed codeset negotiation in 13.10.2.6.

2. There's no indication of what a server should do if the client
delivers a codeset via a CodeSetContext that the server does not support
as a transmission codeset). This isn't likely to happen, but we ought
to close the hole. I propose that we have the server raise
CODESET_INCOMPATIBLE (with a different minor code from 1) in this case
too.

3. Would it be a good idea for us to include recommendations on how to
change a persistent server's native codeset while remaining backwards
compatible with existing IORs floating around the world with obsolete
CodeSetComponent data? Or is it too obvious? (Just make sure the new
server advertises (or at least continues to support) the old native
codeset as a transmission codeset.)

see above