CORBA Notification Service API Reference

Using the CORBA Notification Service

CosNotifyComm::StructuredPushConsumer::Offer_change

Synopsis

Never invoked.

OMG IDL

 void offer_change(
          in CosNotification::EventTypeSeq added,
          in CosNotification::EventTypeSeq removed )
      raises ( InvalidEventType );

Exceptions

CosNotifyComm::InvalidEventType

The subscriber should never raise this exception.

Description

This operation is never invoked. The subscriber application must provide a stubbed-out version of this operation.

Examples

C++ code example:

virtual void offer_change(
      const CosNotification::EventTypeSeq& added,
      const CosNotification::EventTypeSeq& removed )
    {
      throw CORBA::NO_IMPLEMENT();
    }

Exception Minor Codes

This section provides information about the Notification Service exception symbols and minor codes. The minor codes are in the Tobj_Events.idl and Tobj_Notification.idl files. These files are located in the tuxdir\include directory (for Microsoft Windows systems) and tuxdir/include directory (for UNIX systems).

Table 2-4 and Table 2-5 list the exception symbols and corresponding minor codes for the Tobj_Events and Tobj_Notification exceptions respectively. CORBA system events have a minor code field and those minor codes are also defined in these tables.

Note: The exception symbols are organized within the tables by the higher-level exceptions (CORBA::IMP_LIMIT, CORBA::CORBA::BAD_PARAM, CORBA::BAD_INV_ORDER, CORBA::INV_OBHJREF, and CORBA::OBJECT_NOT_EXIST) and listed in alphabetical order.

Table 2-4 Tobj_Events Exception Minor Codes

Exception Symbols	Definitions	Minor Codes (Hexadecimal)
`CORBA::IMP_LIMIT Exceptions`
`Tobj_Events:: POST_DOMAIN_AND_TYPE_TOO_LONG` This exception is raised by: `Tobj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user specified a domain name and type name whose combined length was greater than 31 characters.	5455580D
`Tobj_Events:: POST_DOMAIN_CONTAINS_SEPARATOR` This exception is raised by: `Tobj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user specified a domain name that contained the `"."` character.	54555802
`Tobj_Events::POST_EMPTY_DOMAIN` This exception is raised by: `Tobj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user specified an empty domain name.	5455580B
`Tobj_Events::POST_EMPTY_TYPE` This exception is raised by: `Tobj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user specified an empty type name.	5455580C
`Tobj_Events:: POST_SYSTEM_EVENTS_UNSUPPORTED` This exception is raised by: `Tobj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user tried to post a BEA Tuxedo system event; that is, the domain name is `"TMEVT"` and the type name starts with the `"."` character.	54555804
`Tobj_Events:: POST_TYPE_CONTAINS_SEPARATOR` This exception is raised by: T`obj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user specified a type name that contained the `"."` character.	54555803
`Tobj_Events:: POST_UNSUPPORTED_PRIORITY_VALUE` This is exception is raised by: `Tobj_SimpleEvents:: Channel::push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user added a `"Priority"` field in the variable header. However, the user did not set the field's value to a `"short"` in the range of 1-100.	54555801
`Tobj_Events:: POST_UNSUPPORTED_VALUE_IN_ANY` This exception is raised by: `Tobj_SimpleEvents:: Channel::push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When posting an event, the user put an unsupported type (for example, a structure, union, sequence, etc.) into one of the "anys" in the structured event field. The unsupported type is in the variable header's value field, the filterable data's value field, or the remainder_of_body field.	54555800
`Tobj_Events:: SUB_DOMAIN_AND_TYPE_TOO_LONG` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: connect_structured_push_consumer`	When subscribing, the user specified a domain name and type name whose combined length is greater than 255 characters.	54555809
`Tobj_Events:: SUB_DOMAIN_BEGINS_WITH_SYSEV` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyFilter::Filter:: add_constraints`	When subscribing, the user specified a domain name that begins with the `"."` character.	54555805
Tobj_Events::SUB_EMPTY_DOMAIN This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyFilter::Filter:: add_constraints`	The user specified an empty domain name when subscribing.	54555807
Tobj_Events::SUB_EMPTY_TYPE This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyFilter::Filter:: add_constraints`	The user specified an empty type name when subscribing.	54555808
`Tobj_Events::SUB_FILTER_TOO_LONG` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyFilter::Filter:: add_constraints`	The user specified a data filter expression longer than 255 characters.	5455580A
Tobj_Events::SUB_NAME_TO_LONG This exception is raised by: `Tobj_SimpleEvents::Channel:: push_structured_event` `CosNotifyChannelAdmin:: StructuredProxyPushConsumer:: push_structured_event`	When subscribing, the user specified a subscription name longer than 127 characters.	5455580E
`Tobj_Events:: TRANSIENT_ONLY_CONFIGURATION` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: connect_structured_push_consumer`	The user tried to create a persistent subscription, but the system was configured to support transient subscriptions only.	54555806
`CORBA::BAD_PARAM Exceptions`
`Tobj_Events::INVALID_CHANNEL_ID` This exception is raised by: `Tobj_SimpleEvents::ChannelFactory::find_channel`	When looking up the channel using the Simple Events API, the user specified an invalid channel ID, that is, a channel ID that is not `Tobj_SimpleEvents:: DEFAULT_CHANNEL`.	54555813
`Tobj_Events:: INVALID_SUBSCRIPTION_ID` This exception is raised by: `Tobj_SimpleEvents::Channel:: unsubscribe` `CosNotifyChannelAdmin:: ConsumerAdmin::get_proxy_ supplier` Tobj_SimpleEvents:: Channel::exists	When unsubscribing using the Simple Events API, the user specified an invalid subscription ID, that is, a non-existent or a CosNotification subscription ID. When looking up a subscription using the CosNotification Service API, the user specified an invalid subscription ID, that is, a non-existent or a Simple Events API subscription ID. When calling the `exists` operation using the BEA Simple Events API, the user passed in a CosNotification `subscription_id`.	54555812
`Tobj_Events:: SUB_INVALID_FILTER_EXPRESSION` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyFilter::Filter:: add_constraints`	When subscribing, the user specified an invalid data filter expression. This either means that there is a syntax error in the expression or that one of the field names in the expression is not defined as an FML field. Check that you have correctly created FML field tables that contain all fields that you want to data filter on, and check that the `UBBCONFIG` file is properly configured so that the field table files can be found.	54555810
`Tobj_Events:: SUB_UNSUPPORTED_QOS_VALUE` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: set_qos`	54555811 When subscribing, the user specified an invalid subscription quality of service. For the Simple Events API, this means that the quality of service specified did not meet one of the following requirements: The sequence must be of length one. The name must be `Tobj_SimpleEvents:: SUBSCRIPTION_TYPE`. The value must be either `Tobj_SimpleEvents:: TRANSIENT_SUBSCRIPTION` or `Tobj_SimpleEvents:: PERSISTENT_SUBSCRIPTION`. For the CosNotification Service API, this means that the quality of service specified did not meet one of the following requirements: The quality of service must contain a name/value pair where the name is `Tobj_Notification:: SUBSCRIPTION_TYPE` and the value is `Tobj_Notification:: TRANSIENT_SUBSCRIPTION` or `Tobj_Notification:: PERSISTENT_SUBSCRIPTION`. The quality of service may contain a name/value pair where the name is `Tobj_Notification::SUBSCRIPTION_NAME` and the value is a string containing the subscription's administrative name.
CORBA::INV_OBHJREF
`Tobj_Events:: SUB_NIL_CALLBACK_REF` This exception is raised by: `Tobj_SimpleEvents::Channel:: subscribe` `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: connect_structured_push_consumer`	When subscribing, the user specified a NIL object reference for the callback object which receives events.	54555830

Table 2-5 Tobj_Notification Exception Minor Codes

Exception Symbols	Definitions	Minor Codes (Hexadecimal)
`CORBA::IMP_LIMIT Exceptions`
Tobj_Notification:: SUB_ADD_CONS_ON_TIMED_OUT_FILTER This exception is raised by: `CosNotifyFilter::Filter:: add_constraints`	A CosNotification subscriber waited more than five minutes after creating a filter to call `add_constraints` on the filter. This means that the filter has been destroyed (timed out) and the subscriber must create a new filter.	54555858
Tobj_Notification:: SUB_ADD_CONS_TO_ADDED_FILTER This exception is raised by: `CosNotifyFilter::Filter:: add_constraints`	A CosNotification subscriber called `add_constraints` on a filter that had already been added to a proxy.	5455585E
Tobj_Notification:: SUB_ADDED_TIMED_OUT_FILTER This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: add_filter`	After creating a filter and calling "add_constraints" on it, a CosNotification subscriber waited more than five minutes to call `add_filter` to add the filter to the proxy. This means that the filter has been destroyed (timed out) and that the subscriber must create a new filter.	5455585D
`Tobj_Notification:: SUB_ADD_FILTER_AFTER_CONNECT` This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: add_filter`	A CosNotification subscriber called `add_filter` after connecting to the proxy.	54555852
Tobj_Notification:: SUB_CANT_SET_QOS_AFTER_CONNECT This exception is raised by: `CosNotifyChannelAdmin::StructuredProxyPushSupplier::set_qos`	A CosNotification subscriber called `set_qos` after connecting to the proxy.	54555856
`Tobj_Notification:: SUB_MULTIPLE_CALLS_TO_ADD_CONS` This exception is raised by: `CosNotifyFilter::Filter:: add_constraints`	A CosNotification subscriber called `add_constraints` more than once on a filter.	54555859
Tobj_Notification:: SUB_MULTIPLE_CALLS_TO_SET_FILTER This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: add_filter`	A CosNotification subscriber called `add_filter` more than once on a proxy.	54555851
Tobj_Notification:: SUB_MULTIPLE_CALLS_TO_SET_QOS This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: set_qos`	A CosNotification subscriber called `set_qos` more than once on a proxy.	54555855
Tobj_Notification:: SUB_MULTIPLE_CONSTRAINTS_IN_LIST This exception is raised by: `CosNotifyFilter::Filter:: add_constraints`	When a CosNotification subscriber called `add_constraints` on a filter, the subscriber passed in a list of constraints that had more than one item; that is, the subscriber was trying to send in a list of data filters instead of one data filter.	5455585A
Tobj_Notification:: SUB_MULTIPLE_TYPES_IN_CONSTRAINT This exception is raised by: `CosNotifyFilter::Filter:: add_constraints`	When a CosNotification subscriber called `add_constraints` on a filter, the subscriber passed on a constraint that had more than one domain/type set; that is, the subscriber was trying to send in a list of desired event types instead of one event type.	5455585B
Tobj_Notification:: SUB_NIL_FILTER_REF This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: add_filter`	A CosNotification subscriber passed a NIL filter object reference into `add_filter`.	54555853
Tobj_Notification:: SUB_NO_CUSTOM_FILTERS This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: add_filter`	A CosNotification subscriber passed a filter object that was not created by the default filter factory into `add_filter`. For example, a CosNotification subscriber implemented the `CosNotifyFilter::Filter` interface to do some kind of "custom" filtering and passed one of those filter objects into `add_filter`.	54555854
Tobj_Notification:: SUB_SET_FILTER_NOT_CALLED This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: connect_structured_push_ consumer`	A CosNotification subscriber did not call `add_filter` to the proxy before connecting to the proxy.	54555850
Tobj_Notification:: SUB_SET_QOS_NOT_CALLED This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: connect_structured_push_ consumer`	A CosNotification subscriber did not call `add_filter` to the proxy before connecting to the proxy.	54555857
Tobj_Notification:: SUB_SYSTEM_EVENTS_UNSUPPORTED This exception is raised by: `CosNotifyChannelAdmin:: StructuredProxyPushSupplier:: set_qos`	A CosNotification subscriber passed in a domain name of `"TMEVT"` and a type name that begins with `"."`; that is, the CosNotification subscriber was trying to subscribe to Tuxedo system events. This is not supported. It is only supported by the Simple Events API.	5455585C
Tobj_Notification:: SUB_UNSUPPORTED_CLIENT_TYPE This is exception raised by: `ConsumerAdmin:: obtain_notification_push_ supplier` `SupplierAdmin:: obtain_notification_push_ consumer`	When creating a proxy, a CosNotification subscriber or poster passed in a client type other than `CosNotifyChannelAdmin::STRUCTURED_EVENT`.	5455585F
`CORBA::OBJECT_NOT_EXIST Exception`
Tobj_Notification:: SUBSCRIPTION_DOESNT_EXIST This exception is raised by: `StructuredProxyPushSupplier:: add_filter` `StructuredProxyPushSupplier:: set_qos` `StructuredProxyPushSupplier:: connect_structured_push_ consumer` `StructuredProxyPushSupplier:: disconnect_structured_push_ supplier` Note: `connect_structured_push_ consumer` can raise this exception since a user can create the proxy, then use the `ntsadmin` utility to delete the subscription, and then call `connect_structured_push_ consumer` on the proxy.	A CosNotification subscriber called a method on a proxy that had already been destroyed. The proxy has been destroyed by one of the following actions: The CosNotification subscriber disconnected the proxy. The CosNotification subscriber waited more than five minutes from creating the proxy to connecting it; that is, it took longer than five minutes to complete the subscription. The administrator used the `ntsadmin` utility to destroy the subscription.	54555880