JAV2I14 — Mapping CORBA activity exceptions to Java

The CORBA activity specification (Additional Structuring Mechanisms for
the OTS, v1.0, OMG document formal/02-09-03) introduced three new system
exceptions (INVALID_ACTIVITY, ACTIVITY_COMPLETED, and ACTIVITY_REQUIRED)
that were incorporated into CORBA 3.0.

The JCP J2EE Activity Service for Extended Transactions (JSR 95) adds
three equivalent exceptions
javax.activity.InvalidActivityException
javax.activity.ActivityCompletedException
javax.activity.ActivityRequiredException
to the Java platform.

The Java to IDL mapping should be extended to map these CORBA exceptions
to the equivalent Java activity exceptions, just as the three CORBA
transaction system exceptions are currently mapped to the equivalent
JTA exceptions in the javax.transaction package.

Proposal:

In section 1.4.8, add the following rows to table 1-2:

CORBA Exception RMI Exception
--------------- -------------
INVALID_ACTIVITY javax.activity.InvalidActivityException
ACTIVITY_COMPLETED javax.activity.ActivityCompletedException
ACTIVITY_REQUIRED javax.activity.ActivityRequiredException

No Data Available