TRANS13 — WrongTransaction vs. WRONG_TRANSACTION

Summary: Currently, ORB methods get_response() and get_next_response() throw user
exception
"WrongTransaction". Although this behavior satisfies CORBA 2.2
requirements, it
causes problems. For instance, RequestInterceptor methods, whose
interfaces are fixed
and do not stipulate this exception in their throws clause, cannot
implicitly throw
WrongTransaction. Does it make sense that the ORB throws a user exception
in
this context? We"re wondering whether a mistake was made when the original
requirement
for WrongTransaction (a.k.a., WRONG_TRANSACTION in CORBAServices) was
incorporated
into CORBA. And if not, what was the motivation to make it a user
exception.

duplicate, close issue