Notification Service Avatar
  1. OMG Specification

Notification Service — Open Issues

  • Acronym: NOT
  • Issues Count: 5
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

The Supplier Proxy & Consumer Proxy interfaces don't get ID's

  • Key: NOT13-9
  • Legacy Issue Number: 3521
  • Status: open  
  • Source: Anonymous
  • Summary:

    The interface on EventChanel does not have the ability to get the ChannelId? This
    is quite contrary to the ability on the admin interfaces to retrieve the adminId's.
    Given a proxy to EventChannels's it will be very handy to retrieve the channelId's. The Supplier Proxy & Consumer Proxy interfaces also do not have the ability to get
    the ID's.

  • Reported: NOT 1.2 — Thu, 30 Mar 2000 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Issue with pushing events

  • Key: NOT13-7
  • Legacy Issue Number: 3518
  • Status: open  
  • Source: Anonymous
  • Summary:

    2. Publishers are allowed to push events for the types they have not offered using offer_change().
    This can allow publishers to never advertise the event types they are offerring. For Example, as
    a consumer it can not tell what are the event types that will be offered on the channel.

    Can we require publishers to always call offer_change() on the new event types before pushing them to
    the event channel? If this behavior breaks existing functionality, then how about having push_xxx()
    check to see if the event type is offered, if not add it to the aggregate list?

  • Reported: NOT 1.2 — Thu, 30 Mar 2000 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

The interface on EventChanel does not have the ability to get the ChannelId

  • Key: NOT13-8
  • Legacy Issue Number: 3519
  • Status: open  
  • Source: Anonymous
  • Summary:

    1. The interface on EventChanel does not have the ability to get the ChannelId? This
    is quite contrary to the ability on the admin interfaces to retrieve the adminId's.
    Given a proxy to EventChannels's it will be very handy to retrieve the channelId's.

  • Reported: NOT 1.2 — Thu, 30 Mar 2000 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section 3.4.17. Page:136

  • Key: NOT13-6
  • Legacy Issue Number: 3517
  • Status: open  
  • Source: Anonymous
  • Summary:

    I see the following features lacking in CosNotification spec. What is the process on having this raised as
    an issue, and if all agree add it to the spec in the later revisions. Any info is appreciated.

    1. Section 3.4.17. Page:136. The EventChannel interface in CosNotification, does not allow to retrieve
    its ChannelId. This is unlike the interface on the admins which allow to get the adminids? It would be
    very handy to retrieve the channel id given event channel. I also do not see a way to retrieve
    proxyId's given a consumer proxy or supplier proxy.

  • Reported: NOT 1.2 — Thu, 30 Mar 2000 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Notification service: admin MyChannel attribute

  • Key: NOT13-5
  • Legacy Issue Number: 3175
  • Status: open  
  • Source: Micro Focus ( Bjarne Rasmussen)
  • Summary:

    The notification service administration objects support an attribute
    called MyChannel that returns the event channel that first created the
    administration object. The value type of this attribute is EventChannel.
    For typed administration objects, the typed channel can not be returned
    because a TypedEventChannel is not compatible with an EventChannel. One
    solution is to change the value type of this attribute to a generic
    Object, which can be narrowed to the correct type.

  • Reported: NOT 1.2 — Tue, 4 Jan 2000 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT