NOTJMS 1.0 NO IDEA Avatar
  1. OMG Issue

NOTJMS — Remove read-only attributes from EndpointSender and EndpointReceiver

Open Closed All
  • 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