Common Object Request Broker Architecture Avatar
  1. OMG Specification

Common Object Request Broker Architecture — Closed Issues

  • Acronym: CORBA
  • Issues Count: 40
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
CORBA21-83 3.10.3 Raises Expressions CORBA 1.2 CORBA 2.0 Duplicate or Merged closed
CORBA21-84 CORBA::Bounds and CORBA::TypeCode::Bounds CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-82 Do simple/anonymous types have repository IDs? CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-81 Exception as explicit parameter CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-68 IDL grammar CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-65 7.4 ORB Initialization Last Paragraph - objection CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-67 8.1 Role of the Basic Object Adapter Para 1 - comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-63 7.2.4 Equivalence Checking Operation Paragraph 3 - comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-66 7.4 ORB Initialization Last Paragraph - objection CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-62 7.2.1 Determining the Object Implementation and Interface CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-64 7.2.5 Probing for Object Non-Existence Paragraph 2 - comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-60 6.5.6 Repository Paragraph 4 - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-61 7.1 Converting Object References to Strings Para 3 - comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-57 6.4.3 Interface Objects Paragrapg 1 - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-58 6.4.3 Interface Objects Paragraph 2 - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-59 6.5.4 Container Last Paragraph - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-56 6.3.1 Managing Interface Repositories CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-54 5.2 Explicit Request State: ServerRequest Pseudo Object CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-55 5.3.2 Registering Dynamic Implementation Routines Para 1- comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-52 4.3.3 get_response CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-53 4.6.5 delete_values Paragraph 1 - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-51 4.2.3 invoke CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-50 4.1.2 Memory usage, Para 1, editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-45 2.5 Structure of an Object Adapter CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-47 3.10.3 Raises Expressions CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-49 4.1 Overview, Paragraph 3, editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-48 3.15.2 Object Non-Existence, Para 1, editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-42 CORBA2.0, 1.2.2 Paragraph 2 - comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-44 2.1 Structure of an Object Request Broker CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-43 1.2.2 Requests Paragraph last - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-41 Scope of standard exceptions CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-39 _is_a with CORBA::Object as input parameter CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-40 Unions with enum as discriminator type CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-37 Usage of standard exceptions CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-38 Unqualified names in scopes CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-36 Ambiguity in DII and DSI CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-34 Whether unions carry exact discriminant information CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-46 3.9 Exception Declaration CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-35 Request reuse CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-33 Recusive Type Definitions CORBA 1.2 CORBA 2.0 Resolved closed

Issues Descriptions

3.10.3 Raises Expressions

  • Key: CORBA21-83
  • Legacy Issue Number: 390
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It would make iDL definition of an interface much more complete if they were permitted. X/Open would like OMG to consider permitting listing of Standard Exceptions in raises clauses.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Duplicate or Merged — CORBA 2.0
  • Disposition Summary:

    Duplicate of issue # 389...closed

  • Updated: Fri, 6 Mar 2015 21:34 GMT

CORBA::Bounds and CORBA::TypeCode::Bounds

  • Key: CORBA21-84
  • Legacy Issue Number: 457
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Does Bounds have data members or not? At what scope should Bounds be defined? Given that Bounds exception is also used by Request interface, I suspect what is meant is CORBA::Bounds

  • Reported: CORBA 1.2 — Wed, 13 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    no change to spec., close issue

  • Updated: Fri, 6 Mar 2015 21:34 GMT

Do simple/anonymous types have repository IDs?

  • Key: CORBA21-82
  • Legacy Issue Number: 137
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Do simple types like "long" have specified repository IDs? ("IDL:CORBA/long:1.0") How about anonymous types, like "sequence <long, 10>"?

  • Reported: CORBA 1.2 — Thu, 26 Sep 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    clarified, close issue

  • Updated: Fri, 6 Mar 2015 21:34 GMT

Exception as explicit parameter

  • Key: CORBA21-81
  • Legacy Issue Number: 87
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Is it permissible to declare an exception as an explicit parameter?

  • Reported: CORBA 1.2 — Sun, 18 Aug 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 21:34 GMT

IDL grammar

  • Key: CORBA21-68
  • Legacy Issue Number: 458
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is an inconsistency between the IDL grammar as defined in chapter 3 of CORBA2.0 spec and an IDL example from same chapter(Example p. 3-16..rule 71 and rule 36 specify different

  • Reported: CORBA 1.2 — Thu, 5 Dec 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

7.4 ORB Initialization Last Paragraph - objection

  • Key: CORBA21-65
  • Legacy Issue Number: 453
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: X/Open would like to see either the provision for a system default ORB or an interface that application could use to get list of available ORBs from which to choose.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    No change to the specification. The existing spec supports a default ORB

  • Updated: Fri, 6 Mar 2015 20:58 GMT

8.1 Role of the Basic Object Adapter Para 1 - comment

  • Key: CORBA21-67
  • Legacy Issue Number: 455
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Last sentence: Seems like an odd thing to say. All X/Open specs only guarantee that they are correct if system is configured correctly. Not a big deal

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

7.2.4 Equivalence Checking Operation Paragraph 3 - comment

  • Key: CORBA21-63
  • Legacy Issue Number: 451
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Concept of "type safe narrow" isn"t really described. What"s it"s importance, announcement mechanism, and whether it can be portably relied on by programmers. Where"s more info in spec??

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

7.4 ORB Initialization Last Paragraph - objection

  • Key: CORBA21-66
  • Legacy Issue Number: 454
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Unacceptable to say that "calling the ORB_init function multiple times for the same ORB may be required where an ORB is implemented as a shared library."

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    defer to portability

  • Updated: Fri, 6 Mar 2015 20:58 GMT

7.2.1 Determining the Object Implementation and Interface

  • Key: CORBA21-62
  • Legacy Issue Number: 450
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para 1-comment: These interfaces are very important parts of ORB interface. Their semantics are very unclear. What exceptions are they permitted to raise? Expand on this definition.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

7.2.5 Probing for Object Non-Existence Paragraph 2 - comment

  • Key: CORBA21-64
  • Legacy Issue Number: 452
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para describes implementation strategies that ORB implementors might use to ensure ORBS remain synchronized about presence of objects.Info really appropriate for this spec?

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    no change required, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

6.5.6 Repository Paragraph 4 - editorial

  • Key: CORBA21-60
  • Legacy Issue Number: 436
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The mention of the kind attribute should be bold-face

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

7.1 Converting Object References to Strings Para 3 - comment

  • Key: CORBA21-61
  • Legacy Issue Number: 449
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: it"s not clear from this whether the string generated by object_to_string is portable accross ORBs or among clients. Please add text clarifying portability of generated string.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

6.4.3 Interface Objects Paragrapg 1 - editorial

  • Key: CORBA21-57
  • Legacy Issue Number: 418
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Numbered bullet list following this para is formatted poorly. Text items should be alligned and offset from the numbers in a consistent way

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

6.4.3 Interface Objects Paragraph 2 - editorial

  • Key: CORBA21-58
  • Legacy Issue Number: 419
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Change "...not by modify..." to "...not by modifying..."

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

6.5.4 Container Last Paragraph - editorial

  • Key: CORBA21-59
  • Legacy Issue Number: 433
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The trailing period is missing.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    changed, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

6.3.1 Managing Interface Repositories

  • Key: CORBA21-56
  • Legacy Issue Number: 417
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Paragraph 1 - editorial: Change the reference to "get_interface" to the appropriate type-face

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

5.2 Explicit Request State: ServerRequest Pseudo Object

  • Key: CORBA21-54
  • Legacy Issue Number: 410
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para 4: editorial Change "..OMG IDL for operation.." to "..OMG IDL for the operation...:.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

5.3.2 Registering Dynamic Implementation Routines Para 1- comment

  • Key: CORBA21-55
  • Legacy Issue Number: 411
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Paragraph starts off by explaining that previous versions of CORBA weren"t complete. Not necessary to belabor this point. It"s not clear whether or not this lack has been repaired.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    This is fixed by the new DSI text from the Portability FP

  • Updated: Fri, 6 Mar 2015 20:58 GMT

4.3.3 get_response

  • Key: CORBA21-52
  • Legacy Issue Number: 401
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para 0 - editorial: Add a line containing ");" to the PIDL for get_response, to match the PIDL given in section 4.2.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

4.6.5 delete_values Paragraph 1 - editorial

  • Key: CORBA21-53
  • Legacy Issue Number: 407
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Change "value(s) values" to "value(s)

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

4.2.3 invoke

  • Key: CORBA21-51
  • Legacy Issue Number: 398
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Paragraph 1 - editorial : The leading "c" in create_request is not boldface

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

4.1.2 Memory usage, Para 1, editorial

  • Key: CORBA21-50
  • Legacy Issue Number: 394
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is an extra space between the table reference "Table 21" and the period

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

2.5 Structure of an Object Adapter

  • Key: CORBA21-45
  • Legacy Issue Number: 387
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Paragraph 2, editorial: Change " registration of implementations" to "Registration of implementations"

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

3.10.3 Raises Expressions

  • Key: CORBA21-47
  • Legacy Issue Number: 389
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para last, comment: We understand why standard exceptions may not be listed on a raises expression, but it would make IDL definition of interface more complete if permitted.

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

4.1 Overview, Paragraph 3, editorial

  • Key: CORBA21-49
  • Legacy Issue Number: 392
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Dynamic Invocation Interface is a proper name, and should be capitalized and italicized

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

3.15.2 Object Non-Existence, Para 1, editorial

  • Key: CORBA21-48
  • Legacy Issue Number: 391
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Change "This standard system exception" to "The OBJECT_NOT_EXIST exception", to make explicit which exception is being discussed

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CORBA2.0, 1.2.2 Paragraph 2 - comment

  • Key: CORBA21-42
  • Legacy Issue Number: 384
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para points to C Language Binding chapter and the DII for info on dynamic invocation of objects. It implies that DII is only available in C. Text should pobably be more clear

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

2.1 Structure of an Object Request Broker

  • Key: CORBA21-44
  • Legacy Issue Number: 386
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Paragraph 1, editorial: Change "....up the "request." to "....up the request."

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

1.2.2 Requests Paragraph last - editorial

  • Key: CORBA21-43
  • Legacy Issue Number: 385
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Change "Descriptions of the values and exceptions...." to "For descriptions of the values and exceptions..."

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Scope of standard exceptions

  • Key: CORBA21-41
  • Legacy Issue Number: 132
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Page 3-35 doesn"t really say that the list of standard exceptions belong to the CORBA module, although 3.12 seems to clarify.

  • Reported: CORBA 1.2 — Mon, 23 Sep 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

_is_a with CORBA::Object as input parameter

  • Key: CORBA21-39
  • Legacy Issue Number: 127
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What should _is_a() return when invoking it with an input parameter designating CORBA::Object?

  • Reported: CORBA 1.2 — Mon, 23 Sep 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    closed with revised text

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Unions with enum as discriminator type

  • Key: CORBA21-40
  • Legacy Issue Number: 130
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: How is it possible in IDL to specify a union with an enum discriminator type?

  • Reported: CORBA 1.2 — Mon, 23 Sep 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    no change necessary, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Usage of standard exceptions

  • Key: CORBA21-37
  • Legacy Issue Number: 97
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Is there a difference between standard/system exception? Can an implementation raise both? Is raising a standard exception the recommended way to handle errors while setting an attribute?

  • Reported: CORBA 1.2 — Fri, 6 Sep 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Unqualified names in scopes

  • Key: CORBA21-38
  • Legacy Issue Number: 117
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CORBA says "Once an unqualified name is used in a scope, it cannot be redefined", but my IDL compiler allows it. Is it legal?

  • Reported: CORBA 1.2 — Mon, 23 Sep 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    no change to spec., close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Ambiguity in DII and DSI

  • Key: CORBA21-36
  • Legacy Issue Number: 90
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: For the DII, what value if any can be placed into the Any in the NamedValue corresponding to an OUT parameter? Must it be NULL, or is it legal to include a storage pointer? Also for DSI.

  • Reported: CORBA 1.2 — Thu, 22 Aug 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Whether unions carry exact discriminant information

  • Key: CORBA21-34
  • Legacy Issue Number: 66
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It is uncertain whether or not the explicit value used to discriminate between various arms of a union is information which is required to be supported.

  • Reported: CORBA 1.2 — Mon, 5 Aug 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

3.9 Exception Declaration

  • Key: CORBA21-46
  • Legacy Issue Number: 388
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para 2, editorial: Change "...(as specified by the <member> in its declaration." to "...(as specified by the <member> in its declaration)."

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Request reuse

  • Key: CORBA21-35
  • Legacy Issue Number: 88
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Can a Request pseudo object be invoked multiple times?

  • Reported: CORBA 1.2 — Tue, 20 Aug 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Recusive Type Definitions

  • Key: CORBA21-33
  • Legacy Issue Number: 1
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What does "semantically constrained" mean in section 3.8.2 under the discussion of recursive type specifications.

  • Reported: CORBA 1.2 — Thu, 16 May 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.0
  • Disposition Summary:

    closed issue, resolved

  • Updated: Fri, 6 Mar 2015 20:58 GMT