TRANS 1.3 NO IDEA Avatar
  1. OMG Issue

TRANS13 — WrongTransaction vs. WRONG_TRANSACTION

  • Key: TRANS13-16
  • Legacy Issue Number: 2551
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Currently, ORB methods get_response() and get_next_response() throw user
    "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
    this context? We"re wondering whether a mistake was made when the original
    for WrongTransaction (a.k.a., WRONG_TRANSACTION in CORBAServices) was
    into CORBA. And if not, what was the motivation to make it a user

  • Reported: TRANS 1.1 — Fri, 19 Mar 1999 05:00 GMT
  • Disposition: Resolved — TRANS 1.2
  • Disposition Summary:

    duplicate, close issue

  • Updated: Fri, 6 Mar 2015 21:36 GMT