Issue 4659: Python mapping issue: context                                                                                                                                                                           (python-ftf)
Source: AT&T (Dr. Duncan Grisby, )
Nature: Uncategorized Issue
Severity: 
Summary: The Python mapping for context arguments is slightly unclear. I
suggest adding the following paragraph at the end of section 1.4.1:

  If an operation in an OMG IDL specification has a context
  specification, then a Context parameter follows all
  operation-specific in and inout arguments. The caller must pass a
  CORBA.Context object; if the object has the incorrect type, a
  BAD_PARAM system exception is raised.
Resolution: Accept the proposed changes
Revised Text: Add the following paragraph at the end of section 1.4.1: 
If an operation in an OMG IDL specification has a context specification, then a Context parameter follows all operation-specific in and inout arguments. The caller must pass a CORBA.Context object; if the object has the incorrect type, a BAD_PARAM system exception is raised. 

Actions taken:
November 5, 2001: received issue
October 23, 2002: closed issue
Discussion: 

End of Annotations:=====
To: issues@omg.org
Subject: Python mapping issue: context
From: Duncan Grisby <dgrisby@uk.research.att.com>
Date: Mon, 05 Nov 2001 12:08:30 +0000
Sender: dpg1@uk.research.att.com
Content-Type: text
X-UIDL: O1D!!>bKe9#h%!!$2Q!!

The Python mapping for context arguments is slightly unclear. I
suggest adding the following paragraph at the end of section 1.4.1:

  If an operation in an OMG IDL specification has a context
  specification, then a Context parameter follows all
  operation-specific in and inout arguments. The caller must pass a
  CORBA.Context object; if the object has the incorrect type, a
  BAD_PARAM system exception is raised.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --