org.omg.CosNotifyComm
Interface NotifyPublishOperations

All Known Subinterfaces:
NotifyPublish, ProxyPullConsumer, ProxyPullConsumerOperations, ProxyPushConsumer, ProxyPushConsumerOperations, PullConsumer, PullConsumerOperations, PushConsumer, PushConsumerOperations, SequenceProxyPullConsumer, SequenceProxyPullConsumerOperations, SequenceProxyPushConsumer, SequenceProxyPushConsumerOperations, SequencePullConsumer, SequencePullConsumerOperations, SequencePushConsumer, SequencePushConsumerOperations, StructuredProxyPullConsumer, StructuredProxyPullConsumerOperations, StructuredProxyPushConsumer, StructuredProxyPushConsumerOperations, StructuredPullConsumer, StructuredPullConsumerOperations, StructuredPushConsumer, StructuredPushConsumerOperations, SupplierAdmin, SupplierAdminOperations, TypedProxyPullConsumer, TypedProxyPullConsumerOperations, TypedProxyPushConsumer, TypedProxyPushConsumerOperations, TypedPushConsumer, TypedPushConsumerOperations, TypedSupplierAdmin, TypedSupplierAdminOperations
All Known Implementing Classes:
_NotifyPublishStub, _ProxyPullConsumerStub, _ProxyPushConsumerStub, _PullConsumerStub, _PushConsumerStub, _SequenceProxyPullConsumerStub, _SequenceProxyPushConsumerStub, _SequencePullConsumerStub, _SequencePushConsumerStub, _StructuredProxyPullConsumerStub, _StructuredProxyPushConsumerStub, _StructuredPullConsumerStub, _StructuredPushConsumerStub, _SupplierAdminStub, _TypedProxyPullConsumerStub, _TypedProxyPushConsumerStub, _TypedPushConsumerStub, _TypedSupplierAdminStub, NotifyPublishPOA, NotifyPublishPOATie, ProxyPullConsumerImpl, ProxyPullConsumerPOA, ProxyPullConsumerPOATie, ProxyPushConsumerImpl, ProxyPushConsumerPOA, ProxyPushConsumerPOATie, PullConsumerPOA, PullConsumerPOATie, PushConsumerPOA, PushConsumerPOATie, SequenceProxyPullConsumerImpl, SequenceProxyPullConsumerPOA, SequenceProxyPullConsumerPOATie, SequenceProxyPushConsumerImpl, SequenceProxyPushConsumerPOA, SequenceProxyPushConsumerPOATie, SequencePullConsumerPOA, SequencePullConsumerPOATie, SequencePushConsumerPOA, SequencePushConsumerPOATie, StructuredProxyPullConsumerImpl, StructuredProxyPullConsumerPOA, StructuredProxyPullConsumerPOATie, StructuredProxyPushConsumerImpl, StructuredProxyPushConsumerPOA, StructuredProxyPushConsumerPOATie, StructuredPullConsumerPOA, StructuredPullConsumerPOATie, StructuredPushConsumerPOA, StructuredPushConsumerPOATie, SupplierAdminImpl, SupplierAdminPOA, SupplierAdminPOATie, TypedProxyPullConsumerPOA, TypedProxyPullConsumerPOATie, TypedProxyPushConsumerPOA, TypedProxyPushConsumerPOATie, TypedPushConsumerPOA, TypedPushConsumerPOATie, TypedSupplierAdminPOA, TypedSupplierAdminPOATie

public interface NotifyPublishOperations

The NotifyPublish interface supports an operation which allows a supplier of Notifications to announce, or publish, the names of the types of events it will be supplying, It is intended to be an abstract interface which is inherited by all Notification Service consumer interfaces, and enables suppliers to inform consumers supporting this interface of the types of events they intend to supply.


Method Summary
 void offer_change(EventType[] added, EventType[] removed)
          The offer_change operation takes as input two sequences of event type names: the first specifying those event types which the client of the operation (an event supplier) is informing the target consumer object that it is adding to the list of event types it plans to supply, and the second specifying those event types which the client no longer plans to supply.
 

Method Detail

offer_change

void offer_change(EventType[] added,
                  EventType[] removed)
                  throws InvalidEventType
The offer_change operation takes as input two sequences of event type names: the first specifying those event types which the client of the operation (an event supplier) is informing the target consumer object that it is adding to the list of event types it plans to supply, and the second specifying those event types which the client no longer plans to supply. This operation raises the InvalidEventType exception if one of the event type names supplied in either input parameter is syntactically invalid. In this case, the invalid name is returned in the type field of the exception. Note that each event type name is comprised of two components: the name of the domain in which the event type has meaning, and the name of the actual event type. Also note that either component of a type name may specify a complete domain/event type name, a domain/event type name containing the wildcard ?? character, or the special event type name ?%ALL? described in section 2.6.5 if the specification

Throws:
InvalidEventType