Issue 2213: The section 2.4.5 (notif_service-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: 3) The section 2.4.5 - "A Short-hand Notation for Filtering a Generic Event" is supposed to provide a way of addressing all event types, IMO including typed event transmissions that appear within an Any as a CosNotification::PropertySeq with properties for the operation name and each parameter. Some text should be included which states that $<ident> matches not only $.<ident> for anys, but also $(<ident>) in the case where the any contains a single CosNotification::PropertySeq. Resolution: Added text to end of 2nd to last paragraph in section 2.4.5 (the 2nd change bar on page 47) Revised Text: Actions taken: November 16, 1998: received issue November 16, 1999: closed issue Discussion: Synopsis: It was pointed out that the short-hand notation for filtering generic events described in section 2.4.5 does not clearly indicate the notation can be used to designate typed events that have been wrapped into an Any as a CosNotification::PropertySeq. It was proposed to add text to this section to indicate that $<ident> matches not only $.<ident> for Anys, but also $(<ident>) in the case the Any contains a single CosNotification::PropertySeq. Disposition: I agree with the issue and proposed resolution. Specifically, I propose to modify the last sentence of the 4th paragraph of section 2.4.5 to read: "If no match is found, the translation defaults to either $.variable, or in the case of a CORBA::Any that encapsulates a single unnamed name-value pair list (Sec 2.4.4), $(variable)." VOTE: YES means to add the proposed text; NO means to do nothing End of Annotations:===== Return-Path: To: issues@omg.org Cc: notif_service-rtf@omg.org, Mark Spruiell Errors-to: devnull@dstc.edu.au Reply-to: notif_service-rtf@omg.org Subject: 3 more Notification constraint language issues X-face: *A\_v+D,~Jx_g]`m,s61-x|*;H4hgZeE= Hi all, Here are 3 more Notification Service issues that Mark Spruiell from OOC and I have dug up. 3) The section 2.4.5 - "A Short-hand Notation for Filtering a Generic Event" is supposed to provide a way of addressing all event types, IMO including typed event transmissions that appear within an Any as a CosNotification::PropertySeq with properties for the operation name and each parameter. Suggested resolution: Some text should be included which states that $ matches not only $. for anys, but also $() in the case where the any contains a single CosNotification::PropertySeq. K -- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Keith Duddy : dud at dstc.edu.au : http://www.dstc.edu.au/AU/staff/dud CRC for Distributed Systems Technology (DSTC) General Purpose South, University of Queensland, 4072, Australia ph: +61 7 336 5 4310 :: fx: +61 7 336 5 4311 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2nd edition of my book ``Java Programming with CORBA'' now in bookshops >>> http://www.wiley.com/compbooks/vogel <<< ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Return-Path: Sender: dchang@austin.ibm.com Date: Mon, 16 Nov 1998 10:10:35 -0600 From: David Chang To: notif_service-rtf@omg.org Cc: issues@omg.org, Mark Spruiell Subject: Re: 3 more Notification constraint language issues References: <199811160205.MAA07062@piglet.dstc.edu.au> Keith, My comments to your suggestion is attached to your note. David Chang Keith Duddy wrote: > > Hi all, > > Here are 3 more Notification Service issues that Mark Spruiell from > OOC and I have dug up. > > 1) The term name-value pair is not well defined in the Notification > document. > > Suggested resolution: > > We need to decide as a group to explicitly state that either only > CosNotification::PropertySeq is supported (as well as structutally > equivalent types only when IIOP messages elide member naming or IR > info), OR that any structurally equivalent type is supported. > I would favour the former - as it allows implementers to rely on the > TypeCode::equal() operation to do comparisons portably rather > than doing explicit traversals of the typecode. >> I favour only CosNotification::PropertySeq is supported. > > 2) I note that a footnote on page 34 of the spec says that the term > "name-value pair" is not meant to denote CORBA::NVList, but it > doesn't > actually say what it does mean. This should be fixed too (before > table > 2.2 where it's used first). > > Suggested resolution: > > As above - the footnote should state that the term "name-value pair" > refers to CosNotification::PropertySeq. >> Agree > > 3) The section 2.4.5 - "A Short-hand Notation for Filtering > a Generic Event" is supposed to provide a way of addressing all > event > types, IMO including typed event transmissions that appear within an > Any as a CosNotification::PropertySeq with properties for the > operation name and each parameter. > > Suggested resolution: > > Some text should be included which states that $ matches not > only $. for anys, but also $() in the case where the > any > contains a single CosNotification::PropertySeq. Agree > > K > -- > > ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: > Keith Duddy : dud at dstc.edu.au : > http://www.dstc.edu.au/AU/staff/dud > CRC for Distributed Systems Technology (DSTC) > General Purpose South, University of Queensland, 4072, Australia > ph: +61 7 336 5 4310 :: fx: +61 7 336 5 4311 > > ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: > 2nd edition of my book ``Java Programming with CORBA'' now in > bookshops > >>> http://www.wiley.com/compbooks/vogel <<< > > :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::