Notification/JMS Interworking Service Avatar
  1. OMG Specification

Notification/JMS Interworking Service — Closed Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
NOTJMS-4 Remove read-only attributes from EndpointSender and EndpointReceiver NOTJMS 1.0b1 NOTJMS 1.0 Resolved closed
NOTJMS-3 Adding InvalidExternalEndpoint Exception to new Bridge::start_bridge() ope NOTJMS 1.0b1 NOTJMS 1.0 Resolved closed
NOTJMS-2 Rename two operations in the Bridge interface NOTJMS 1.0b1 NOTJMS 1.0 Resolved closed
NOTJMS-1 Remove the CosEventDomainAdmin::NotificationStyle NOTJMS 1.0b1 NOTJMS 1.0 Resolved closed

Issues Descriptions

Remove read-only attributes from EndpointSender and EndpointReceiver

  • Key: NOTJMS-4
  • Legacy Issue Number: 6342
  • Status: closed  
  • Source: ZettaScale Technology ( Dr. Ramzi Karoui)
  • Summary:

    Removing the read-only attributes from EndpointSender and EndpointReceiver from the Bridge Interface and replacing them by two external ExternalEndpoints.

    The Bridge interface change from:
    interface Bridge

    { readonly attribute EndpointReceiver end_point_receiver; readonly attribute EndpointSender end_point_sender; void start () raises (BridgeAlreadyStarted); void stop () raises (BridgeInactive); status get_status(); void destroy (); }

    to:
    interface Bridge

    { readonly attribute ExternalEndpoint end_point_receiver; readonly attribute ExternalEndpoint end_point_sender; void start_bridge () raises (BridgeAlreadyStarted,InvalidExternalEndPoints); void stop_bridge () raises (BridgeInactive); status get_status(); void destroy (); }

    The EndpointReceiver and EndpointSender types should be removed from the IDL also.

    The rational behind this change is that the EndpointReceiver and EndpointSender object interfaces were exposing internal implementation parts that no third party needs to have access to. Removing those interfaces from the public IDL of the bridge improves the bridge security.

    Note that for the purposes of connection the bridge implementation has to manage internally these objects and publish their interfaces to the appropriate Notification Service or JMS.
  • Reported: NOTJMS 1.0b1 — Mon, 20 Oct 2003 04:00 GMT
  • Disposition: Resolved — NOTJMS 1.0
  • Disposition Summary:

    Accept proposed resolution
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Adding InvalidExternalEndpoint Exception to new Bridge::start_bridge() ope

  • Key: NOTJMS-3
  • Legacy Issue Number: 6341
  • Status: closed  
  • Source: ZettaScale Technology ( Dr. Ramzi Karoui)
  • Summary:

    Adding InvalidExternalEndpoint Exception to new Bridge::start_bridge() operation.
    · The Bridge::start_bridge operation is now raises two exceptions: BridgeAdlreadyStarted and InvalidExternalEndpoint.
    The rational behind this extension is that during Bridge::start_bridge operation, consumer and publisher are created. If any ExternalEndpoint information (be it source or sink) is invalid, client cannot be created, thus InvalidExternalEndpoint will be raised
  • Reported: NOTJMS 1.0b1 — Mon, 20 Oct 2003 04:00 GMT
  • Disposition: Resolved — NOTJMS 1.0
  • Disposition Summary:

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

Rename two operations in the Bridge interface

  • Key: NOTJMS-2
  • Legacy Issue Number: 6340
  • Status: closed  
  • Source: ZettaScale Technology ( Dr. Ramzi Karoui)
  • Summary:

    Rename two operations in the Bridge interface name have been made:
    · Original Name; Bridge::start(); New Name: Bridge::start_bridge()
    · Original Name; Bridge::stop(); New Name: Bridge::stop_bridge()
    The Start and stop names are common operation names. Those names may clash with other implementation components.

  • Reported: NOTJMS 1.0b1 — Mon, 20 Oct 2003 04:00 GMT
  • Disposition: Resolved — NOTJMS 1.0
  • Disposition Summary:

    Accept proposed changes
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Remove the CosEventDomainAdmin::NotificationStyle

  • Key: NOTJMS-1
  • Legacy Issue Number: 6339
  • Status: closed  
  • Source: ZettaScale Technology ( Dr. Ramzi Karoui)
  • Summary:

    Removing the CosEventDomainAdmin::NotificationStyle by CosBridgeAdmin::FlowStyle, defined hereafter :
    enum FlowStyle

    { PUSH, PULL }

    . The rational for that is to avoid having dependencies with the CosEventDomainAdmin module defined in the Event domain manager specification. In fact, few notification service providers provide today this CoS.

  • Reported: NOTJMS 1.0b1 — Mon, 20 Oct 2003 04:00 GMT
  • Disposition: Resolved — NOTJMS 1.0
  • Disposition Summary:

    No Data Available
  • Updated: Fri, 6 Mar 2015 20:58 GMT