Common Object Request Broker Architecture Avatar
  1. OMG Specification

Common Object Request Broker Architecture — Closed Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
CORBA34-451 Ordering of user exception and return values CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-269 Multiple objects on a stream CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-270 Definition of stream portability CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-273 Lifecycle Key type definition CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-272 Stream contexts and internalization CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-271 Start and end of context tags CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-264 Coordinator remembering LockCoordinator CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-263 Input values for "which" arg of non-trans. LockCoordinator CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-265 Freeing of locks at the end of a transaction CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-266 Getting the thread ID in a non-transactional lock request CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-267 Communication failure issue CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-268 Timeout while locking CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-255 CosCompoundExternalization Service CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-256 $issue.summary CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-257 $issue.summary CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-260 CosGraphs::deep CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-261 Common format on stream CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-259 performing a compound copy of relationship CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-258 $issue.summary CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-262 Using local thread identification for concurrency CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-253 CosCompoundExternalization Service (3) CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-254 CosCompoundExternalization Service (2) CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-244 QueryCollection::Collection -- finding index CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-245 Query Collection::Collection -- Sharing State CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-247 QueryCollection::Collection -- membership scoping CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-246 QueryCollection::Collection -- Adding multiple elements CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-237 Questions on CosQuery::QueryableCollection interfaces CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-240 QueryCollection::Collection -- reset() exceptions CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-238 QueryCollection::Collection -- keyed collections CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-239 QueryCollection::Collection -- next_n() CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-241 QueryCollection::Collection -- destroy methods CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-243 QueryCollection::Collection -- Iterator Position Invalid CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-242 QueryCollection::Collection -- iterator updating CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-229 Query language for operations CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-232 Definition of NULL in datafiles without NULL as a concept CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-230 Delegating iterator functionality to the RDBMS CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-233 Clarification request for section 11.1.5 CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-231 retrieve_element CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-234 How do iterators handle changing of the data they are pointing at CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-236 Use of MD5 on arguments CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-235 Updating information via query iterators CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-224 WWW Form output CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-225 Malformed PropertyName CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-228 OQS relation to POS CORBA 1.2 CORBA 3.4 Deferred closed
CORBA34-216 Compiler being able to translate from OMG-IDL into ANSI CORBA 1.2 CORBA 3.4 Deferred closed
CORBA23-234 CODESET_INCOMPATIBLE exception is not defined CORBA 1.2 CORBA 2.3 Resolved closed
CORBA23-232 Wide String (and String encoding) CORBA 1.2 CORBA 2.3 Resolved closed
CORBA23-231 IDL TypeExtension correction CORBA 1.2 CORBA 2.3 Resolved closed
CORBA23-233 IDL Type Extensions: DATA_CONVERSION exception CORBA 1.2 CORBA 2.3 Resolved closed
CORBA23-220 DII operations "get_response and get_next_response CORBA 1.2 CORBA 2.3 Resolved closed
CORBA23-219 6.5.6. Repository Paragraph 2 - objection CORBA 1.2 CORBA 2.3 Closed; No Change closed
CORBA21-84 CORBA::Bounds and CORBA::TypeCode::Bounds CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-83 3.10.3 Raises Expressions CORBA 1.2 CORBA 2.0 Duplicate or Merged 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-67 8.1 Role of the Basic Object Adapter Para 1 - 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-65 7.4 ORB Initialization Last Paragraph - objection 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-63 7.2.4 Equivalence Checking Operation Paragraph 3 - comment 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-61 7.1 Converting Object References to Strings Para 3 - 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-59 6.5.4 Container Last Paragraph - 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-57 6.4.3 Interface Objects Paragrapg 1 - 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-55 5.3.2 Registering Dynamic Implementation Routines Para 1- comment 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-53 4.6.5 delete_values Paragraph 1 - editorial CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-52 4.3.3 get_response 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-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-47 3.10.3 Raises Expressions CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-46 3.9 Exception Declaration 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-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-42 CORBA2.0, 1.2.2 Paragraph 2 - comment CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-41 Scope of standard exceptions 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-39 _is_a with CORBA::Object as input parameter CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-38 Unqualified names in scopes CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-37 Usage of standard exceptions CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-36 Ambiguity in DII and DSI CORBA 1.2 CORBA 2.0 Resolved closed
CORBA21-35 Request reuse 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-33 Recusive Type Definitions CORBA 1.2 CORBA 2.0 Resolved closed
CORBA22-52 6.6.4 Pragma Directives for RepositoryId Para 1 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-51 6.6.1 OMG IDL Format Paragraph 5 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-56 6.7.2 TypeCode Constants Last Paragraph - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-55 6.7.1 The Type Code Interface Paragraph 4 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-54 6.7.1 The TypeCode Interface All Paragraphs - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-53 6.7 TypeCodes Paragraph 3 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-57 CORE spec reference CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-50 6.5.22 InterfaceDef Paragraphs 7 and 8 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-49 6.5.22 InterfaceDef Paragraph 6 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-48 6.5.20 AttributeDef Paragraph 2 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-38 6.5.4 Container Paragraph 6 - editorial CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-37 6.5.4 Container Paragraph 5 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-36 6.5.4 Container Paragraph 2 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-35 6.5.3 Contained Paragraph 10 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-43 6.5.4 Container Paragraph 15 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-42 6.5.4 Container Paragraph 12 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-46 6.5.10 StructDef Last paragraph - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-45 6.5.8 ConstantDef Interface Paragraph 2 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-40 6.5.4 Container Paragraph 10 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-39 6.5.4 Container Paragraph 8 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-44 6.5.6 Repository Paragraph 4 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-47 6.5.11 UnionDef Last Paragraph - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-41 6.5.4 Container Paragraph 11 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-34 6.5.3 Contained - Paragraph 7 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-33 6.5.3 Contained Paragraph 2 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-32 6.5.2 IRObject Paragraph 3 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-22 4.6 Context Object Operations, Para 2 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-21 4.2.2 add_arg Paragraph 5-comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-24 4.6.2 set_on_value Paragraph 2 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-23 4.3.1 sen3 - comment 23 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-28 4.6.4 get_values Paragraph 5 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-27 4.6.4 get_values Paragraph 4 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-26 4.6.4 get_values Paragraph 2 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-25 4.6.3 set_values CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-18 4.1.1 Common Data Structures, Paragraph 6, comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-17 Interface for managing interceptors is missing CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-31 6.4.3 Interface Objects Paragraph 3 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-30 4.6.7 delete Paragraph 4 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-20 4.2.1 create_request Paragraph 8 - comment CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-19 4.1.3 Return Status and Exceptions CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-29 4.6.5 delete_values Paragraph 3 - objection CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-4 Do typecodes need literal constant representations in all mappings? CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-3 Missing info about the semantics of ORB_init and OA_init CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-14 Similar structure to IR::Identifier CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-13 Pseudo-IDL identifiers differ by case only CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-8 Typecodes for recursive sequences CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-7 lookup() questions CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-10 DSI and oneway operations CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-9 ServerRequest::op_def() CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-6 Interface Repository Error Handling CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-5 CORBA::InterfaceDef name collision CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-12 Apparent error in CORBA 2.0 Interoperability CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-11 Repository IDs CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-16 Portability and the #include directive CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-15 Recursive sequence TypeCodes CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-2 IFR: union elements associated with case labels CORBA 1.2 CORBA 2.2 Resolved closed
CORBA22-1 Inheritance of describe_contents() CORBA 1.2 CORBA 2.2 Resolved closed

Issues Descriptions

Ordering of user exception and return values

  • Legacy Issue Number: 16
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The COM/CORBA Part A spec states that user exceptions go after return values in one place, and before return values in another. (3.2.10.3 and 4.1.3.1)

  • Reported: CORBA 1.2 — Fri, 14 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 22:00 GMT

Multiple objects on a stream

  • Legacy Issue Number: 22
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What happens when multiple calls are made to Stream::externalize() at the top level? Does the stream contain all those objects, and how does a client discover this?

  • Reported: CORBA 1.2 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Definition of stream portability

  • Legacy Issue Number: 21
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The standard stream format should specify that it is portable across different ORBs and hardware, but not across streamable object implementations whch use different semantic content.

  • Reported: CORBA 1.2 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Lifecycle Key type definition

  • Legacy Issue Number: 18
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Several LifeCycle methods take a "key" argument, but do not clarify whether multiple NameComponents are allowed in a key, if ordering matters, etc.

  • Reported: CORBA 1.2 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Stream contexts and internalization

  • Legacy Issue Number: 19
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The Externalization spec does not state how a stream implementation is to discover that a context exists when internalizing an object.

  • Reported: CORBA 1.2 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Start and end of context tags

  • Legacy Issue Number: 20
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The standard stream data format does not define tags to be used to identify the beginning and end of a context.

  • Reported: CORBA 1.2 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Coordinator remembering LockCoordinator

  • Legacy Issue Number: 59
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CosTransactions Coordinator does not have any IDL method to remember LockCoordinator. How does it know what Lock Coordinators should be informed to drop locks?

  • Reported: CORBA 1.2 — Wed, 24 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Input values for "which" arg of non-trans. LockCoordinator

  • Legacy Issue Number: 60
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: For a non-transactional client who wants to get a LockCoordinator, what input values should one use for the "which argument?

  • Reported: CORBA 1.2 — Wed, 24 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Freeing of locks at the end of a transaction

  • Legacy Issue Number: 58
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It is not clear whether CosTransactions::Coordinator is responsible for freeing locks at the end of a transaction.

  • Reported: CORBA 1.2 — Wed, 24 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Getting the thread ID in a non-transactional lock request

  • Legacy Issue Number: 57
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In a non-transactional lock request, the lock identity is supposedly based on thread ID. How can the server code get the client thread ID when they may be on different machines?

  • Reported: CORBA 1.2 — Wed, 24 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Communication failure issue

  • Legacy Issue Number: 56
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: If the ORB suffered a communication failure while LockSet::lock() is being called, how does the client know if the lock was granted or not?

  • Reported: CORBA 1.2 — Tue, 23 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Timeout while locking

  • Legacy Issue Number: 47
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: If the ORB times out while LockSet::lock() is being called, how does the client know if the lock was granted or not?

  • Reported: CORBA 1.2 — Tue, 2 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

CosCompoundExternalization Service

  • Legacy Issue Number: 476
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: When Node::externalize_node is called, is node responsible for externalizing related object? What happens, if related object isn"t a CosStream::Streamable?

  • Reported: CORBA 1.2 — Tue, 21 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

${issue.summary}

  • Legacy Issue Number: 473
  • Status: closed  
  • Source: Anonymous
  • Summary:
  • Reported: CORBA 1.2 — Wed, 8 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

${issue.summary}

  • Legacy Issue Number: 472
  • Status: closed  
  • Source: Anonymous
  • Summary:
  • Reported: CORBA 1.2 — Wed, 8 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

CosGraphs::deep

  • Legacy Issue Number: 469
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: If CosGraphs::deep propagation value is encountered, is the Node"s related object supposed to get copied, too. What if LifeCycleObject delegates to CosCompoundLifeCycle::Operations?

  • Reported: CORBA 1.2 — Fri, 3 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Common format on stream

  • Legacy Issue Number: 466
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: When reading a stream, there is no way of telling where context (limited to calls to begin_context and end_context) end and a new one starts.. Resolved problem with new "tag-byte" 0xFF.

  • Reported: CORBA 1.2 — Thu, 19 Dec 1996 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

performing a compound copy of relationship

  • Legacy Issue Number: 470
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The second pass of operation is to "cause the node and all of its roles" to be copied. How do you get related object of the NEW roles to be the New Node?

  • Reported: CORBA 1.2 — Fri, 3 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

${issue.summary}

  • Legacy Issue Number: 471
  • Status: closed  
  • Source: Anonymous
  • Summary:
  • Reported: CORBA 1.2 — Thu, 9 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Using local thread identification for concurrency

  • Legacy Issue Number: 61
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It seemed more useful for the concurrency service to be non-IDL, and just based on local thread identification.

  • Reported: CORBA 1.2 — Wed, 24 Jul 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

CosCompoundExternalization Service (3)

  • Legacy Issue Number: 478
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: When internalizing a relationships, how do the "shallow" nodes and roles get included?

  • Reported: CORBA 1.2 — Tue, 21 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

CosCompoundExternalization Service (2)

  • Legacy Issue Number: 477
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Role in new node are disconnected It"s role of read_graph to correctly establish new relationships. How is that accomplished?

  • Reported: CORBA 1.2 — Tue, 21 Jan 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- finding index

  • Legacy Issue Number: 6
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: On CollectionObj->remove_element_at(IteratorRef), how does the collection "know" the index?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Query Collection::Collection -- Sharing State

  • Legacy Issue Number: 5
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: How do IteratorObjs and CollectionObjs share state?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- membership scoping

  • Legacy Issue Number: 3
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: I assume that we are allowed to scope membership in a collection via an interface test (e.g, must be rooted off of Collection) and throw an InvalidElement exception?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- Adding multiple elements

  • Legacy Issue Number: 4
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Using collection factories, can you add multiple elements at once, and/or add new create methods?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Questions on CosQuery::QueryableCollection interfaces

  • Legacy Issue Number: 13
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Clarifications on interfaces which support QueryableCollection.

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- reset() exceptions

  • Legacy Issue Number: 10
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Can an iterator "reset()" throw an exception such as IteratorPositionInvalid if it is wrapping a db cursor which has no facility for reset?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- keyed collections

  • Legacy Issue Number: 12
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Is it correct to offer the vanilla collection methods and add a new set for keyed access?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- next_n()

  • Legacy Issue Number: 11
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Can an interator have a next_n()? Or is this supposed to be via subtyping the interface?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- destroy methods

  • Legacy Issue Number: 9
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Where are the destroy methods on the Iterator or on the Collection?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- Iterator Position Invalid

  • Legacy Issue Number: 7
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What does the IteratorPositionInvalid exception mean? Is it only that the user has cycled through the list elements and that no reset() has been issued?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

QueryCollection::Collection -- iterator updating

  • Legacy Issue Number: 8
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: How does the Iterator know to become invalid when the Collection is altered?

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

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Query language for operations

  • Legacy Issue Number: 83
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Need all operations on the Collection be made using the SQL-92/QOL-93? If so, how is it possible to handle flat file datastores?

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Definition of NULL in datafiles without NULL as a concept

  • Legacy Issue Number: 80
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 11.4.2 para. 3 says that FieldValues may be NULL. What if my datastore is a flat file without a concept of NULL. Does NULL take on the value of empty string for flat files?

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Delegating iterator functionality to the RDBMS

  • Legacy Issue Number: 82
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Is there a way that I can delegate the functionality of the Iterators to the RDBMS itself?

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Clarification request for section 11.1.5

  • Legacy Issue Number: 79
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Several of the bullets in section 11.1.5 are unclear.

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

retrieve_element

  • Legacy Issue Number: 81
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: How does this operation work?

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

How do iterators handle changing of the data they are pointing at

  • Legacy Issue Number: 78
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Is it not possible that objects in a collection could have changed in between calls to the iterator accessing them?

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Use of MD5 on arguments

  • Legacy Issue Number: 23
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Appendix D states that a challenge structure consists of the MD5 of the arguments, but does not specify how the arguments are laid into a stream of octets for the MD5 algorithm.

  • Reported: CORBA 1.2 — Wed, 26 Jun 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Updating information via query iterators

  • Legacy Issue Number: 69
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: When using iterator operations like adding, inserting, etc., how are changes reflected back to the datastores?

  • Reported: CORBA 1.2 — Tue, 13 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

WWW Form output

  • Legacy Issue Number: 535
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Issue regarding implementation of the Query IDL specifications on a Java ORB. Issue involves implementing following idl definition from the CosQueryCollection module

  • Reported: CORBA 1.2 — Thu, 6 Mar 1997 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Malformed PropertyName

  • Legacy Issue Number: 284
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It is not believed that the spec ever defines what a "malformed" PropertyName is. The closest definition is in para on page 26, section 5.1.1.2 and is not much help

  • Reported: CORBA 1.2 — Sat, 19 Oct 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

OQS relation to POS

  • Legacy Issue Number: 84
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Need the OQS have any interface with the POS? I don"t see how the two can be interfaced.

  • Reported: CORBA 1.2 — Thu, 15 Aug 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

Compiler being able to translate from OMG-IDL into ANSI

  • Legacy Issue Number: 184
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Existing software based on messages with ASNI format description and a future version based on IDL. Does anybody know something about such a compiler?

  • Reported: CORBA 1.2 — Mon, 14 Oct 1996 04:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

CODESET_INCOMPATIBLE exception is not defined

  • Legacy Issue Number: 495
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CODESET_INCOMPATIBLE is not defined in CORBA 2.0, and so must be added to the list of standard exceptions in section 3.15.1

  • Reported: CORBA 1.2 — Tue, 4 Feb 1997 05:00 GMT
  • Disposition: Resolved — CORBA 2.3
  • Disposition Summary:

    resolved is current core 2.3 draft, issue closed

  • Updated: Sun, 8 Mar 2015 21:42 GMT

Wide String (and String encoding)

  • Legacy Issue Number: 140
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Are the string lengths number of bytes or characters (in 3.1.2 of orbos/96-02-03)?

  • Reported: CORBA 1.2 — Tue, 1 Oct 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.3
  • Disposition Summary:

    resolved in current 2.3 draft, close issue

  • Updated: Sun, 8 Mar 2015 21:42 GMT

IDL TypeExtension correction

  • Legacy Issue Number: 131
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is an error in the grammar as written, so that you cannot (for example) have attributes of type wstring.

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

    resolved in Core 2.3 draft, close dissue

  • Updated: Sun, 8 Mar 2015 21:42 GMT

IDL Type Extensions: DATA_CONVERSION exception

  • Legacy Issue Number: 494
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Algorithm on p. 27 says to raise DATA_CONVERSION exception, but textual description on p. 28 par 1 specifies CODESET_INCOMPATIBLE exception when client and server native codesets aren"t compatible

  • Reported: CORBA 1.2 — Tue, 4 Feb 1997 05:00 GMT
  • Disposition: Resolved — CORBA 2.3
  • Disposition Summary:

    resolved is current 2.3 draft, closed issue

  • Updated: Sun, 8 Mar 2015 21:42 GMT

DII operations "get_response and get_next_response

  • Legacy Issue Number: 464
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Both operations permit the flag CORBA::RESP_NO_WAIT to be set. How is is invoker being informed that there is no response available? Incorrect to use exception.

  • Reported: CORBA 1.2 — Wed, 18 Dec 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.3
  • Disposition Summary:

    resolved, closed issue

  • Updated: Sat, 7 Mar 2015 02:37 GMT

6.5.6. Repository Paragraph 2 - objection

  • Legacy Issue Number: 434
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para indicates that there may be more than 1 interface Repository in any given environment. How can portable application determine this, and how can it determine what the requirements are?

  • Reported: CORBA 1.2 — Tue, 26 Nov 1996 05:00 GMT
  • Disposition: Closed; No Change — CORBA 2.3
  • Disposition Summary:

    the application should use either the naming or trading service to determine which IR to use.

  • Updated: Sat, 7 Mar 2015 02:37 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

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

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

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.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.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

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

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.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.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.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

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.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.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.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.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

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

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.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.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

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

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

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

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

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

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

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

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

_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

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

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

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

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

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

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

6.6.4 Pragma Directives for RepositoryId Para 1 - objection

  • Key: CORBA22-52
  • Legacy Issue Number: 444
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Conforming compilers should ignore pragmas that are not defined. in this spec, and that they do not explicitly support. Portable applications should only use pragmas defined in this spec.

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

    The proposal in the summary is unreasonably restrictive, and would disallow use of other pragmas i

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

6.6.1 OMG IDL Format Paragraph 5 - comment

  • Key: CORBA22-51
  • Legacy Issue Number: 443
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The semantics of minor version number changes should be a requirement on conforming applications (objects).

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

    That"s what the sections appears to say. close issue, no change

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

6.7.2 TypeCode Constants Last Paragraph - comment

  • Key: CORBA22-56
  • Legacy Issue Number: 448
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para indicates that form of TypeCode constants might be implementation specific.Does that mean the contents of the TypeCode implementation as opposed to signature of programmer?

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

    Offending language has been removed in Revision 2.3

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

6.7.1 The Type Code Interface Paragraph 4 - comment

  • Key: CORBA22-55
  • Legacy Issue Number: 447
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Last sentence: It"s not clear under which conditions this is permitted. It"s permitted when a structure,union,enumeration or alias typecode wasn"t obtained from Interface Repository.

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

    Fixed in 2.2 close no change

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

6.7.1 The TypeCode Interface All Paragraphs - objection

  • Key: CORBA22-54
  • Legacy Issue Number: 446
  • Status: closed  
  • Source: Anonymous
  • 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.

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

    Fixed in 2.2 close no change.

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

6.7 TypeCodes Paragraph 3 - objection

  • Key: CORBA22-53
  • Legacy Issue Number: 445
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It"s better to say "However, TypeCode "literals" shall have a representation such that they can be placed in C include files."

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

    Offending sentence removed in the resolution of issue 73. This is the same as issue 73

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

CORE spec reference

  • Key: CORBA22-57
  • Legacy Issue Number: 459
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CORE contains specific language binding information which should be in a language binding chapter or in a new appendix

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

    Such information now exists only in the way of examples of what a particular piece of pseudo-IDL me

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

6.5.22 InterfaceDef Paragraphs 7 and 8 - comment

  • Key: CORBA22-50
  • Legacy Issue Number: 442
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: These paras indicate that an error is returned if the ID already exists in the repository. What is the error and what happens of the IR supports versioning?

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

    Superceded by 778

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

6.5.22 InterfaceDef Paragraph 6 - comment

  • Key: CORBA22-49
  • Legacy Issue Number: 441
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This Para indicates that the base_interface attribute can return an error if there are name conflicts. What error is returned?

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

    Subsumed by 778

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

6.5.20 AttributeDef Paragraph 2 - comment

  • Key: CORBA22-48
  • Legacy Issue Number: 440
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What does the describe operation return for this interface?

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

    Add the sentence "The describe operation for an AttributeDef object returns an AttributeDescription

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

6.5.4 Container Paragraph 6 - editorial

  • Key: CORBA22-38
  • Legacy Issue Number: 427
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para starts the description of the arguments for the lookup_name operation. It should stand out more instead of being intended in such a way that it looks like part of previous item"s description.

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

    changed, close issue

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

6.5.4 Container Paragraph 5 - comment

  • Key: CORBA22-37
  • Legacy Issue Number: 426
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para descibes exclude_inherited argumentto the content operation. Format is poor, it"s not clear what the default setting for this argument might be (if any).

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

    no change required, close issue

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

6.5.4 Container Paragraph 2 - objection

  • Key: CORBA22-36
  • Legacy Issue Number: 425
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It"s not clear what lookup operation returns when it is successful. We can tell from the IDL, but it should be explicitly defined. We think it returns object reference to scoped name.

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

    no change required, close issue

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

6.5.3 Contained Paragraph 10 - comment

  • Key: CORBA22-35
  • Legacy Issue Number: 424
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para indicates that name attribute is changed to new_name, and version attribute is changed to new_version. If name already exists and IR doesn"t support versioning=error. What error?

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

    Subsumed by 778 . Closed with that annotation

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

6.5.4 Container Paragraph 15 - comment

  • Key: CORBA22-43
  • Legacy Issue Number: 432
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para describes create_<type> operations. It indicates that there are errors returned under differing circumstances. Possible errors should be defined.

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

    Superceded by 778

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

6.5.4 Container Paragraph 12 - comment

  • Key: CORBA22-42
  • Legacy Issue Number: 431
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para refers to the describe operation. This operation is part of the parent interface from which container interface is inherited.There should be a pointer to the parent interface

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

    Close no change

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

6.5.10 StructDef Last paragraph - comment

  • Key: CORBA22-46
  • Legacy Issue Number: 438
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para indicates that the type member is ignored and that it should be set to TC_void. If it is ignored, why should it be set to anything?

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

    Remove the phrase "is ignored" from the last sentence of section 8.5.9 rev 2.2

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

6.5.8 ConstantDef Interface Paragraph 2 - comment

  • Key: CORBA22-45
  • Legacy Issue Number: 437
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There should be a pointer to the list of simple types.

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

    Replace the phrase "simple type( ..... )" by the phrase "primitive types allowed in a constant decl

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

6.5.4 Container Paragraph 10 - comment

  • Key: CORBA22-40
  • Legacy Issue Number: 429
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This para and para 4 both describe a limiy_type argument. These should be described in the same way since they appear to have the same semantics

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

    Incorporate resolution and close issue.

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

6.5.4 Container Paragraph 8 - comment

  • Key: CORBA22-39
  • Legacy Issue Number: 428
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What other values of levels_to_search are legal? What happens if values other than those described are used?Is an exception raised? If so, what exception?

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

    resolved, close issue

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

6.5.6 Repository Paragraph 4 - comment

  • Key: CORBA22-44
  • Legacy Issue Number: 435
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This Para refers to a PrimitiveDef. There should be a pointer to where this is defined.

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

    In section 8.5.6 second para under Read Interface, add a cross reference to section 8.5.13 where Pr

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

6.5.11 UnionDef Last Paragraph - comment

  • Key: CORBA22-47
  • Legacy Issue Number: 439
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This Para indicates that the type member is ignored and that it should be set to TC_void. If it is ignored, why should it be set to anything?

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

    Incorporate resolution and close issue

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

6.5.4 Container Paragraph 11 - comment

  • Key: CORBA22-41
  • Legacy Issue Number: 430
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Same as issue # 429 with respect to 6.5.4 Container Paragraph 5.

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

    Incorporate resolution and close issue.

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

6.5.3 Contained - Paragraph 7 - comment

  • Key: CORBA22-34
  • Legacy Issue Number: 423
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This initial Para of the Write Interface section indicates that an error is returned if an object with specified ID attribute already exists. Error should be specified.

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

    Close with annotation as above.

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

6.5.3 Contained Paragraph 2 - comment

  • Key: CORBA22-33
  • Legacy Issue Number: 422
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Para indicates that IRs are not required to support simultaneous containment of multiple versions of the same named object. Required that IRs are able to handle multiple versions of objects

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

    resolved, close issue

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

6.5.2 IRObject Paragraph 3 - objection

  • Key: CORBA22-32
  • Legacy Issue Number: 421
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Write Interface description indicates that it is error to invoke destroy on a Repository or PrimitiveDef. Should state that behavior is undefined.

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

    close issue, resolved

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

4.6 Context Object Operations, Para 2 - objection

  • Key: CORBA22-22
  • Legacy Issue Number: 399
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Spec reads " Property names are stored preserving their case, however names cannot differ simply by their case." This sentence should be deleted.

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

    Propose to apply resolution as above and close issue in 2.3

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

4.2.2 add_arg Paragraph 5-comment

  • Key: CORBA22-21
  • Legacy Issue Number: 397
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: X/Open believes there is no need to use different wording. They don"t believe that it is useful to indicate that mixing of methods might be allowed someday

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

    In Section 5.2.2 Para 5 Rev 2.2 remove the word "currently" from the last sentence

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

4.6.2 set_on_value Paragraph 2 - objection

  • Key: CORBA22-24
  • Legacy Issue Number: 402
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Text reads:"Currently, only string values are supported by the context object." Sentence should be deleted, since PIDL requires that a string be the value provided

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

    Propose apply resolution to rev 2.3 and close issue

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

4.3.1 sen3 - comment 23 - comment

  • Key: CORBA22-23
  • Legacy Issue Number: 400
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: X/Open recommends that this para is being reworded to require that applications call get_response after a send. Spec could also be modified to detect errors if response is not required

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

    close issue, no change

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

4.6.4 get_values Paragraph 5 - objection

  • Key: CORBA22-28
  • Legacy Issue Number: 406
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Text reads " If the specified scope name is not found, an exception is returned." Error to be indicated must be specified. See objection for Paragraph 2.

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

    See resolution of 404

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

4.6.4 get_values Paragraph 4 - objection

  • Key: CORBA22-27
  • Legacy Issue Number: 405
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Text indicates that "Value scope names are implementation-specific." Items not necessary for portable development of applications are unspecified,undefined.

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

    Remove paragraph 4. Does not add any value to the spec.

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

4.6.4 get_values Paragraph 2 - objection

  • Key: CORBA22-26
  • Legacy Issue Number: 404
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The error to be returned must be specified.. Since a status is not required to be returned, it"s incorrect to say that error is returned. Exception is raised.

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

    add text to sections 5.6.4, 5.6.5 and 5.6.7 stating what exceptions are raised under what condition

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

4.6.3 set_values

  • Key: CORBA22-25
  • Legacy Issue Number: 403
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: See comment on set_value in issue # 402

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

    Propose apply resolution to rev 2.3 and close issue

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

4.1.1 Common Data Structures, Paragraph 6, comment

  • Key: CORBA22-18
  • Legacy Issue Number: 393
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The usage of len could easily lead to a situation where it was inconsistent with TypeCode through erronous usage. WOuld be great if standard System exception was available for this case.

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

    Close no change in 2.3a

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

Interface for managing interceptors is missing

  • Key: CORBA22-17
  • Legacy Issue Number: 380
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: List of interceptors to be called during request and order in which interceptor will be called: Needs to be resolved by Alec Thomas but shouls also be moved to ORB RFT

  • Reported: CORBA 1.2 — Mon, 18 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.2
  • Disposition Summary:

    close no change

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

6.4.3 Interface Objects Paragraph 3 - comment

  • Key: CORBA22-31
  • Legacy Issue Number: 420
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Final Para describes the types of support interfaces that might be available in some implementations. These are not interesting for portable application develpoment.

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

    no change necessary, issue closed

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

4.6.7 delete Paragraph 4 - objection

  • Key: CORBA22-30
  • Legacy Issue Number: 409
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The exception to be returned is not specified. See objection for 4.6.4 get_values Paragraph 2.

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

    see resolution of 404

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

4.2.1 create_request Paragraph 8 - comment

  • Key: CORBA22-20
  • Legacy Issue Number: 396
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This paragraph should be deleted, since it is not useful for an application programmer.

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

    issue closed, no change

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

4.1.3 Return Status and Exceptions

  • Key: CORBA22-19
  • Legacy Issue Number: 395
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: X/Open recommends that the specification is being modified to require DII functions to return a Status as an unsigned long. Implementations without return value return value:non-conforming

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

    closed issue, resolved

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

4.6.5 delete_values Paragraph 3 - objection

  • Key: CORBA22-29
  • Legacy Issue Number: 408
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: This paragraph indicates that an exception is returned. See objection for 4.6.4 get_values Paragraph 2

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

    see resolution of 404

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

Do typecodes need literal constant representations in all mappings?

  • Key: CORBA22-4
  • Legacy Issue Number: 73
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 6.7 of the CORBA 2 spec constrains the representation of typecodes such that typecode "literals" can be placed in C include files. Is this meant?

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

    The offending paragraph, which is now the para 3 of section 10.7, seems to not clearly state anythi

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

Missing info about the semantics of ORB_init and OA_init

  • Key: CORBA22-3
  • Legacy Issue Number: 68
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The text associated with ORB_init and OA_init does not specify what is done with the argv parameter that requires it to be inout.

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

    Incorporate change in 2.3a and close issue.

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

Similar structure to IR::Identifier

  • Key: CORBA22-14
  • Legacy Issue Number: 283
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is no such type as IR::Identifier? It should really say CORBA::Identifier. Are ServiceTypeNames limited to characters allowed in IDL Identifier and also case sensitive?

  • Reported: CORBA 1.2 — Sat, 19 Oct 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.2
  • Disposition Summary:

    resolved in 2.2

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

Pseudo-IDL identifiers differ by case only

  • Key: CORBA22-13
  • Legacy Issue Number: 233
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: IDL identifiers in chapter 4 differ by case only [Ch 17 CORBA2.0] Some of the identifiers used in the IDL in Ch 4 differ only by case, which is not legal in IDL.

  • Reported: CORBA 1.2 — Mon, 14 Oct 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.2
  • Disposition Summary:

    No Data Available

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

Typecodes for recursive sequences

  • Key: CORBA22-8
  • Legacy Issue Number: 116
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In the interface for the create_recursive_sequence_tc ORB method, is this just a matter of creating a TypeCode with these two fields, or is there a parameter missing?

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

    No parameter is missing. you just create a TypeCode with TCKind set to tk_sequence and content type

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

lookup() questions

  • Key: CORBA22-7
  • Legacy Issue Number: 86
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Does the lookup() function also lookup in the base interfaces if used on an InterfaceDef? If so, what if it is is more than one interface? Can the search_name argument be a scoped name?

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

    resolved, close issue

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

DSI and oneway operations

  • Key: CORBA22-10
  • Legacy Issue Number: 129
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: After calling a Dynamic Invocation Routine, how can the ORB know whether to send a response back to the client (i.e., whether the operation was "oneway")?

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

    The ORB uses protocol information (i.e. from GIOP response_expected) to make this decision.

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

ServerRequest::op_def()

  • Key: CORBA22-9
  • Legacy Issue Number: 128
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: What is the purpose of the ServerRequest::op_def method? It is not described in the Chap. 5 discussion of ServerRequest or in 18.4.1.

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

    close issue, no change

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

Interface Repository Error Handling

  • Key: CORBA22-6
  • Legacy Issue Number: 85
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The IR specification specifies what operations are an error, but does not specify how this error is returned. The specification does not define any exceptions.

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

    Superceded by Issue 778

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

CORBA::InterfaceDef name collision

  • Key: CORBA22-5
  • Legacy Issue Number: 76
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CORBA::InterfaceDef defines an operation "is_a", although there is already an "is_a" operation defined in CORBA::Object. Section 3.6 on page 3-17 says this is not allowed.

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

    close issue, resolved

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

Apparent error in CORBA 2.0 Interoperability

  • Key: CORBA22-12
  • Legacy Issue Number: 156
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: in 13.5.6 "The DCE ESIOP", "Location Policy Component" there is for module IOP a list of 4 "const octet statements.. The BNF appears to suggest that this is invalid.

  • Reported: CORBA 1.2 — Tue, 8 Oct 1996 04:00 GMT
  • Disposition: Resolved — CORBA 2.2
  • Disposition Summary:

    issue closed, no change

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

Repository IDs

  • Key: CORBA22-11
  • Legacy Issue Number: 133
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: I would expect a lookup on IDL:/CORBA/Object:1.0 to return an InterfaceDef. It would seem more logical if Object was represented by a "default" InterfaceDef in the repository.

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

    resolved, close issue

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

Portability and the #include directive

  • Key: CORBA22-16
  • Legacy Issue Number: 306
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: #include has same definition that C and C++ programmers are used to.HP treats #include at global scope as merely introducing declarations. This idea needs closer examination

  • Reported: CORBA 1.2 — Sat, 23 Nov 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.2
  • Disposition Summary:

    close no change in 2.4

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

Recursive sequence TypeCodes

  • Key: CORBA22-15
  • Legacy Issue Number: 300
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Are they a new TypeCode kind (tk_kind) or are they of the tk_sequence TypeCode kind/

  • Reported: CORBA 1.2 — Tue, 29 Oct 1996 05:00 GMT
  • Disposition: Resolved — CORBA 2.2
  • Disposition Summary:

    subsumed by issue 116, close issue.

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

IFR: union elements associated with case labels

  • Key: CORBA22-2
  • Legacy Issue Number: 14
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: A union element associated with N case labels manifests in the IFR as N distinct UnionMembers. Is this intended?

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

    resolved, close issue

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

Inheritance of describe_contents()

  • Key: CORBA22-1
  • Legacy Issue Number: 2
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Where does the OperationDef interface inherit the describe_contents() operation from.

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

    close issue, resolved

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