Issue 446:  6.7.1 The TypeCode Interface  All Paragraphs - objection (orb_revision)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: PIDL for this interface describes the exceptions that might be raised, but the text doesn"t define the conditions when all of those exceptions might occur. This must be addressed.

Resolution:  Fixed in 2.2 close no change.
Revised Text: 
Actions taken:
November 26, 1996: received issue
February 23, 1999: closed issue
Discussion: 

End of Annotations:=====
eturn-Path: <mchapman@iona.com>
From: Martin Chapman <mchapman@iona.com>
Date: Thu, 21 Aug 1997 12:18:36 +0100
To: Paul Rabin <rabin@opengroup.org>
CC: orb_revision@omg.org
Subject: [tcross@iona.com: IFR issues at OMG]

Paul,
As promised at a conf call a few weeks ago, we have looked at the
currently logged IFR issues. Terence Cross trawled through them and
here is his response (marked TC>). Terence can be available for a core
rtf conf
call to try and resolve these. Let us know when its on the agenda.

Martin.
----
Report on open IFR issues at OMG 2.1 task force
-----------------------------------------------
General
-------

A call needs to be made as to whether or not
IDL definned exceptions should be included in the IFR
module.  It would be quite a large change but would be more
in-line with other services to add IFR specific exceptions.

Also I had thought that I raised an issue about repository IDs,
that the default format would include a null prefix
followed by a slash.  I dont see it there can I raise it now?

Also another issue is that I cant see any operations that
allow for the creation of ExceptionDef objects.
I would expect the following within interface Container:

ExceptionDef create_exception (
	    in RepositoryId id,
	    in Identifier name,
	    in VersionSpec version,
	    in StructMemberSeq members
	    );

Issue 446: 6.7.1 The TypeCode Interface All Paragraphs - objection

Source: The Open Group (Mr. Paul Rabin, )
Nature: Uncategorized
Severity: 
Summary: PIDL for this interface describes the exceptions that might
be
raised, but the text doesn't define the conditions when all of those
exceptions might occur. This must be addressed.
Resolution: 
Actions taken:
11/26/1996: received issue

TC> It seems clear enough that Bad Kind is for ops on the wrong tc
TC> and bounds is when the index for structured types is too large.
TC> Be more specific.