Two things:

In general it should be enough to catch a
CORBA::SystemException. We don't really care which
one it is in most places anyway and this will
catch both, COMM_FAILURE and TRANSIENT (plus 27
others).

For debugging purposes it would be nice to have a
detailed report of all 29 exceptions that can
happen. The probelm I see is: How to make this
convinient for the developer? The only thing I can
think of to do that would be a macro
CATCH_AND_LOG_CORBA_EXEPTIONS which gets expanded
to that huge block of catch(es)... not nice, but
betten then rewritting that block all over the
place and forgetting something while doing so.