Issue 2121: Another issue related to suspend/resume connection (notif_service-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: I would like to register another issue related to suspend_connection and resume_connection. I feel a new exception should be defined for each of these operations, to cover the case in which a client invokes one of these operations on a Proxy which has not yet been connected to by a client. Currently, it is possible for a client to invoke one of these operations on a Proxy that is not connected to a client, but there is no appropriate exception to raise. Resolution: Revised Text: Actions taken: October 27, 1998: received issue February 23, 1999: closed issue Discussion: End of Annotations:===== Return-Path: From: "Michael J. Greenberg" Subject: Another issue related to suspend/resume connection... To: issues@omg.org, notify_service-rtf@omg.org Date: Tue, 27 Oct 1998 11:35:25 -0500 (EST) Hello, I would like to register another issue related to suspend_connection and resume_connection. I feel a new exception should be defined for each of these operations, to cover the case in which a client invokes one of these operations on a Proxy which has not yet been connected to by a client. Currently, it is possible for a client to invoke one of these operations on a Proxy that is not connected to a client, but there is no appropriate exception to raise. Specifically, I propose the following modification to their signatures: module CosNotifyChannelAdmin { ... exception ConnectionNotActive {}; interface AnyInterfaceThatIncludesTheseOperations { ... void suspend_connection () raises (ConnectionAlreadyInactive, ConnectionNotActive); void resume_connection raises (ConnectionAlreadyActive, ConnectionNotActive); }; // AnyInterfaceThatIncludesTheseOperations }; // CosNotifyChannelAdmin -Mike -- Michael J. Greenberg NEC Systems Lab. 4 Independence Way Tel. 609-734-6142 Princeton, NJ 08540 Fax. 609-734-6001 mjg@syl.nj.nec.com