Issue 1666: 6.8.3.1 C++ Example of Generated Poller (messaging-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: Issue Summary: Update Messaging specification for compliance with Objects by Value RTF 1.1 report. Issue Detail: The specification syntax and example generated code for using Objects by Value is at best compliant with the OBV 1.0 spec, and in some cases would need revision for compliance with that specification. Update the spec to be compliant with the ObV RTF intended for publication in CORBA 2.3. Resolution: Revised Text: ) Change all editorial mentions of value (in the context of OBV) to valuetype. I started to enumerate these but had got to about 15 instances in 2 pages, and got fed up. I hope the RTF will indulge us to make such such a proposal. 2) Change all mentions of the keyword value in IDL to the keyword valuetype. 3) Change the definition of Generic Exception Holder in section 6.4.1 from module Messaging { value ExceptionHolder { boolean is_system_exception; boolean byte_order; sequence<octet> marshaled_exception; }; }; to module Messaging { typedef sequence <octet> octSeq; valuetype ExceptionHolder { private boolean is_system_exception; private boolean byte_order; private octSeq marshaled_exception; }; }; 4) The definition of Generic Poller Value in Section 6.6 has already been "nearly" fixed in the resolution to Issue 3071. The only thing remaining is to make the data private. Change from module Messaging { valuetype Poller : CORBA::Pollable { readonly attribute Object operation_target; readonly attribute string operation_name; attribute ReplyHandler associated_handler; readonly attribute boolean is_from_poller; Object target; string op_name; }; }; to module Messaging { valuetype Poller : CORBA::Pollable { readonly attribute Object operation_target; readonly attribute string operation_name; attribute ReplyHandler associated_handler; readonly attribute boolean is_from_poller; private Object target; private string op_name; }; }; 5) Make the corresponding changes in the consolidated IDL. 6) Change code examples to be conformant with the language mapping for valuetypes Actions taken: July 13, 1998: received issue January 9, 2001: closed issue Discussion: 1) Change all editorial mentions of value (in the context of OBV) to valuetype. I started to enumerate these but had got to about 15 instances in 2 pages, and got fed up. I hope the RTF will indulge us to make such such a proposal. 2) Change all mentions of the keyword value in IDL to the keyword valuetype. 3) Change the definition of Generic Exception Holder in section 6.4.1 from module Messaging { value ExceptionHolder { boolean is_system_exception; boolean byte_order; sequence<octet> marshaled_exception; }; }; to module Messaging { typedef sequence <octet> octSeq; valuetype ExceptionHolder { private boolean is_system_exception; private boolean byte_order; private octSeq marshaled_exception; }; }; 4) The definition of Generic Poller Value in Section 6.6 has already been "nearly" fixed in the resolution to Issue 3071. The only thing remaining is to make the data private. Change from module Messaging { valuetype Poller : CORBA::Pollable { readonly attribute Object operation_target; readonly attribute string operation_name; attribute ReplyHandler associated_handler; readonly attribute boolean is_from_poller; Object target; string op_name; }; }; to module Messaging { valuetype Poller : CORBA::Pollable { readonly attribute Object operation_target; readonly attribute string operation_name; attribute ReplyHandler associated_handler; readonly attribute boolean is_from_poller; private Object target; private string op_name; }; }; 5) Make the corresponding changes in the consolidated IDL. 6) Change code examples to be conformant with the language mapping for valuetypes End of Annotations:===== Return-Path: Sender: "Jon Goldberg" Date: Fri, 10 Jul 1998 17:51:22 -0700 From: Jon Goldberg To: hans.kneubuehl@ubs.com CC: messaging-rtf@omg.org, issues@omg.org Subject: Re: 6.8.3.1 C++ Example of Generated Poller References: Hi- Rather than opening the specific issue stated by Hans, I'd like to open the more general Messaging issue: Issue Summary: Update Messaging specification for compliance with Objects by Value RTF 1.1 report. Issue Detail: The specification syntax and example generated code for using Objects by Value is at best compliant with the OBV 1.0 spec, and in some cases would need revision for compliance with that specification. Update the spec to be compliant with the ObV RTF intended for publication in CORBA 2.3. take care, Jon hans.kneubuehl@ubs.com wrote: > > According to CORBA Objects by Value the generated member functions > should be pure virtual, but they are only virtual in the example in > 6.8.3.1. > > Regards > Hans Sender: Chris.Smith@uab.ericsson.se Message-ID: <389AFD28.566A68B4@uab.ericsson.se> Date: Fri, 04 Feb 2000 17:24:08 +0100 From: Chris Smith X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i686) MIME-Version: 1.0 To: messaging-rtf@omg.org Subject: Re: Messaging Issue 1666 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: N<9!!7~)e9V(\d91S/e9 > Issue 1666: 6.8.3.1 C++ Example of Generated Poller (messaging-rtf) > Summary: Summary: Issue Summary: Update Messaging specification for > compliance with Objects by Value RTF 1.1 report. > Issue Detail: The specification syntax and example generated code > for using Objects by Value is at best compliant with the > OBV 1.0 spec, and in some cases would need revision for compliance > with that specification. Update the spec to be compliant > with the ObV RTF intended for publication in CORBA 2.3. We were waiting for a big "all in one" proposal from Matt Mihic on the valueType bits, but since this doesnt seem to be forthcoming, perhaps its better to fix this in piecemeal fashion. As far I am concerned the following fixes are roughly in the direction we need. 1) Change all editorial mentions of value (in the context of OBV) to valuetype. I started to enumerate these but had got to about 15 instances in 2 pages, and got fed up. I hope the RTF will indulge us to make such such a proposal. 2) Change all mentions of the keyword value in IDL to the keyword valuetype. 3) Change the definition of Generic Exception Holder in section 6.4.1 from module Messaging { value ExceptionHolder { boolean is_system_exception; boolean byte_order; sequence marshaled_exception; }; }; to module Messaging { typedef sequence octSeq; valuetype ExceptionHolder { private boolean is_system_exception; private boolean byte_order; private octSeq marshaled_exception; }; }; 4) The definition of Generic Poller Value in Section 6.6 has already been "nearly" fixed in the resolution to Issue 3071. The only thing remaining is to make the data private. Change from module Messaging { valuetype Poller : CORBA::Pollable { readonly attribute Object operation_target; readonly attribute string operation_name; attribute ReplyHandler associated_handler; readonly attribute boolean is_from_poller; Object target; string op_name; }; }; to module Messaging { valuetype Poller : CORBA::Pollable { readonly attribute Object operation_target; readonly attribute string operation_name; attribute ReplyHandler associated_handler; readonly attribute boolean is_from_poller; private Object target; private string op_name; }; }; 5) Make the corresponding changes in the consolidated IDL. From: hans.kneubuehl@ubs.com X-OpenMail-Hops: 2 Date: Fri, 18 Feb 2000 18:02:15 +0100 Message-Id: Subject: Re: Messaging Issue 1666 MIME-Version: 1.0 TO: messaging-rtf@omg.org, uabcsru@uab.ericsson.se Content-Disposition: inline; filename="BDY.TXT" ;Creation-Date="Fri, 18 Feb 2000 18:02:15 +0100" Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII ;Creation-Date="Fri, 18 Feb 2000 18:02:15 +0100" X-UIDL: NB:!!Z~>!!;L!"!e]4e9 Hi Chris I think the compliance to Objects by Value is to a large degree an editorial issue. suggestion: Couldn't someone just make available a version including all editorial fixes for valuetype conformance change bared, so we can have a look at whether some fixes have been missed or wrong. Also, if there are any changes that are beyond editorial fixes they can be raised as a new issue. I agree to your suggested fixes. I would just like to add 6) Change the code examples to be conformant with the language mapping for valuetypes. Regards Hans > -----Original Message----- > From: uabcsru [mailto:uabcsru@uab.ericsson.se] > Sent: Friday, February 04, 2000 5:24 PM > To: messaging-rtf > Cc: uabcsru > Subject: UNAUTHENTICATED: Re: Messaging Issue 1666 > > > > Issue 1666: 6.8.3.1 C++ Example of Generated Poller > (messaging-rtf) > > Summary: Summary: Issue Summary: Update Messaging > specification for compliance with Objects by Value RTF 1.1 report. > > Issue Detail: The specification syntax and example > generated code for using Objects by Value is at best > compliant with the > > OBV 1.0 spec, and in some cases would need revision for > compliance with that specification. Update the spec to be compliant > > with the ObV RTF intended for publication in CORBA 2.3. > > We were waiting for a big "all in one" proposal from Matt > Mihic on the valueType bits, but since this doesnt seem > to be forthcoming, perhaps its better to fix this in > piecemeal fashion. As far I am concerned the following fixes > are roughly in the direction we need. > > > > 1) Change all editorial mentions of value (in the context > of OBV) to valuetype. I started to enumerate these but > had got to about 15 instances in 2 pages, and got fed > up. I hope the RTF will indulge us to make such such a > proposal. > > 2) Change all mentions of the keyword value in IDL to > the keyword valuetype. > > 3) Change the definition of Generic Exception Holder > in section 6.4.1 from > > module Messaging { > value ExceptionHolder { > boolean is_system_exception; > boolean byte_order; > sequence marshaled_exception; > }; > }; > > to > > module Messaging { > typedef sequence octSeq; > valuetype ExceptionHolder { > private boolean is_system_exception; > private boolean byte_order; > private octSeq marshaled_exception; > }; > }; > > 4) The definition of Generic Poller Value in > Section 6.6 has already been "nearly" fixed in the > resolution to Issue 3071. The only thing remaining > is to make the data private. Change from > > module Messaging { > valuetype Poller : CORBA::Pollable { > readonly attribute Object operation_target; > readonly attribute string operation_name; > attribute ReplyHandler associated_handler; > readonly attribute boolean is_from_poller; > Object target; > string op_name; > }; > }; > > to > > module Messaging { > valuetype Poller : CORBA::Pollable { > readonly attribute Object operation_target; > readonly attribute string operation_name; > attribute ReplyHandler associated_handler; > readonly attribute boolean is_from_poller; > private Object target; > private string op_name; > }; > }; > > 5) Make the corresponding changes in the consolidated IDL. > From: hans.kneubuehl@ubs.com X-OpenMail-Hops: 2 Date: Fri, 18 Feb 2000 18:02:15 +0100 Message-Id: Subject: Re: Messaging Issue 1666 MIME-Version: 1.0 TO: messaging-rtf@omg.org, uabcsru@uab.ericsson.se Content-Disposition: inline; filename="BDY.TXT" ;Creation-Date="Fri, 18 Feb 2000 18:02:15 +0100" Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII ;Creation-Date="Fri, 18 Feb 2000 18:02:15 +0100" X-UIDL: NB:!!Z~>!!;L!"!e]4e9 Hi Chris I think the compliance to Objects by Value is to a large degree an editorial issue. suggestion: Couldn't someone just make available a version including all editorial fixes for valuetype conformance change bared, so we can have a look at whether some fixes have been missed or wrong. Also, if there are any changes that are beyond editorial fixes they can be raised as a new issue. I agree to your suggested fixes. I would just like to add 6) Change the code examples to be conformant with the language mapping for valuetypes. Regards Hans > -----Original Message----- > From: uabcsru [mailto:uabcsru@uab.ericsson.se] > Sent: Friday, February 04, 2000 5:24 PM > To: messaging-rtf > Cc: uabcsru > Subject: UNAUTHENTICATED: Re: Messaging Issue 1666 > > > > Issue 1666: 6.8.3.1 C++ Example of Generated Poller > (messaging-rtf) > > Summary: Summary: Issue Summary: Update Messaging > specification for compliance with Objects by Value RTF 1.1 report. > > Issue Detail: The specification syntax and example > generated code for using Objects by Value is at best > compliant with the > > OBV 1.0 spec, and in some cases would need revision for > compliance with that specification. Update the spec to be compliant > > with the ObV RTF intended for publication in CORBA 2.3. > > We were waiting for a big "all in one" proposal from Matt > Mihic on the valueType bits, but since this doesnt seem > to be forthcoming, perhaps its better to fix this in > piecemeal fashion. As far I am concerned the following fixes > are roughly in the direction we need. > > > > 1) Change all editorial mentions of value (in the context > of OBV) to valuetype. I started to enumerate these but > had got to about 15 instances in 2 pages, and got fed > up. I hope the RTF will indulge us to make such such a > proposal. > > 2) Change all mentions of the keyword value in IDL to > the keyword valuetype. > > 3) Change the definition of Generic Exception Holder > in section 6.4.1 from > > module Messaging { > value ExceptionHolder { > boolean is_system_exception; > boolean byte_order; > sequence marshaled_exception; > }; > }; > > to > > module Messaging { > typedef sequence octSeq; > valuetype ExceptionHolder { > private boolean is_system_exception; > private boolean byte_order; > private octSeq marshaled_exception; > }; > }; > > 4) The definition of Generic Poller Value in > Section 6.6 has already been "nearly" fixed in the > resolution to Issue 3071. The only thing remaining > is to make the data private. Change from > > module Messaging { > valuetype Poller : CORBA::Pollable { > readonly attribute Object operation_target; > readonly attribute string operation_name; > attribute ReplyHandler associated_handler; > readonly attribute boolean is_from_poller; > Object target; > string op_name; > }; > }; > > to > > module Messaging { > valuetype Poller : CORBA::Pollable { > readonly attribute Object operation_target; > readonly attribute string operation_name; > attribute ReplyHandler associated_handler; > readonly attribute boolean is_from_poller; > private Object target; > private string op_name; > }; > }; > > 5) Make the corresponding changes in the consolidated IDL. >