Issue 5471: In the resolution of issue 4659 (python-ftf)
Source: Hewlett-Packard (Dr. Jishnu Mukerji, jishnu(at)hp.com)
Nature: Uncategorized Issue
Severity: 
Summary: 1. In the resolution of issue.... 


(a) The system exception that is raised is said to be BAD_PARAM. Since
it is a bad context that is being taken exception to, why is the
BAD_CONTEXT exception not used instead?


(b) It is better to also define a standard minor code with an associated
error description when a use of a standard system exception is
specified. This helps the user figure out what caused the system
exception to be triggered. This is missing in the resolution.

Resolution: 
Revised Text: 
Actions taken:
July 9, 2002: received issue
Discussion: 

End of Annotations:=====
Date: Tue, 09 Jul 2002 16:18:41 -0400 
From: Jishnu Mukerji <jishnu_mukerji@hp.com> 
Organization: Hewlett-Packard 
X-Mailer: Mozilla 4.79 [en] (Win98; U) 
X-Accept-Language: en 
To: issues@omg.org 
Subject: Issue for Python Language Mapping RTF 


An issue that I brought up prior to the AB meeting regarding the
Python
RTF (not a show stopper):


1. In the resolution of issue.... 


(a) The system exception that is raised is said to be BAD_PARAM. Since
it is a bad context that is being taken exception to, why is the
BAD_CONTEXT exception not used instead?


(b) It is better to also define a standard minor code with an
associated
error description when a use of a standard system exception is
specified. This helps the user figure out what caused the system
exception to be triggered. This is missing in the resolution.


Jishnu