Issue 7217: Mapping CORBA activity exceptions to Java                                                                                                                                                               (java2idl-rtf)
Source: International Business Machines (Mr. Simon C. Nash, nash@hursley.ibm.com)
Nature: Uncategorized Issue
Severity: 
Summary: 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
Resolution: 
Revised Text: 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
Actions taken:
April 2, 2004: received issue
July 30, 2007: closed issue
Discussion: 
Closed, accepted. See revised text below
End of Annotations:=====
Date: Fri, 02 Apr 2004 22:22:59 +0100 
From: Simon Nash <nash@hursley.ibm.com> 
Organization: IBM 
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) 
X-Accept-Language: en 
To: issues@omg.org 
CC: java2idl-rtf@omg.org 
Subject: 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


   Simon
-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com


Date: Thu, 16 Nov 2006 19:02:29 .
From: Simon Nash <nash@hursley.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Jishnu Mukerji <jishnu@hp.com>, Ken Cavanaugh <Ken.Cavanaugh@sun.com>,
        Jeffrey Mischkinsky <jmischki@wheel.dcn.davis.ca.us>,
        Yoshitaka Honishi <honi@jp.fujitsu.com>, Andy Piper <andyp@bea.com>,
        Naveed Shaikh <Naveed.Shaikh@borland.com>,
        Bill Beckwith <bill.beckwith@ois.com>, Eoghan Glynn <eglynn@iona.com>
CC: java2idl-rtf@omg.org
Subject: Proposed resolution for Java to IDL issue 7217


Here is a proposed resolution for issue 7217.


Issue title:


Mapping CORBA activity exceptions to Java


Issue summary:


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


  Simon
-- 
Simon C Nash   IBM Distinguished Engineer
Hursley Park, Winchester, UK   nash@hursley.ibm.com
Tel. +44-1962-815156   Fax +44-1962-818999