| ▼Ccom::pcbsys::nirvana::client::nAbstractChannel | This is the base class for all nirvana channel types, including queues and normal pub/sub channels and as such has no public methods |
| Ccom::pcbsys::nirvana::client::nChannel | This class is a Nirvana channel, offering the Nirvana channel related services |
| Ccom::pcbsys::nirvana::client::nQueue | This class provides a Queue mechanism |
| Ccom::pcbsys::nirvana::client::nAsyncExceptionListener | This interface should be implemented by classes wishing to register to receive asynchronous errors from the nirvana server |
| ▼Ccom::pcbsys::nirvana::client::nBaseClientException | This exception forms the base for all client exceptions |
| Ccom::pcbsys::nirvana::client::nChannelAlreadyExistsException | This exception is thrown if a user tries to make a channel that already exists |
| Ccom::pcbsys::nirvana::client::nChannelAlreadySubscribedException | The user has tried to subscribe to the channel more than once |
| Ccom::pcbsys::nirvana::client::nChannelNotFoundException | The specified channel could not be located on the server |
| Ccom::pcbsys::nirvana::client::nDuplicateJoinException | The user has requested a join be created but the server already has this join configured in the database |
| Ccom::pcbsys::nirvana::client::nExceededLimitException | The number of events in the current transaction has exceeded the server configuration |
| Ccom::pcbsys::nirvana::client::nIllegalArgumentException | This class defines the error that can be thrown by passing an illegal argument to any method of any class in the nirvana client API |
| Ccom::pcbsys::nirvana::client::nIllegalChannelModeException | This exception is thrown if a user tries calls queue specific functionality on a channel object or channel specific functionality on a queue object |
| Ccom::pcbsys::nirvana::client::nIllegalStateException | This exception is thrown if a Channel or Queue is in an illegal state for specific functionality to be offered |
| Ccom::pcbsys::nirvana::client::nNameAlreadyBoundException | This exception is thrown if a user attempts to create a named client context on a channel or queue that is already in use |
| Ccom::pcbsys::nirvana::client::nNameDoesNotExistException | This exception is thrown if a user attempts to delete a named client context on a channel or queue that does not exist |
| Ccom::pcbsys::nirvana::client::nNameSpaceConflictException | There is a conflict in the name space and the attempted operation failed |
| Ccom::pcbsys::nirvana::client::nRealmAlreadyBoundException | You have tried to bind a realm that the server already has been bound |
| Ccom::pcbsys::nirvana::client::nRealmInUseException | This exception is thrown when an attempt is made to remove a realm from another realm when the realm is part of a cluster or has channels that are joined in the requesting realm |
| Ccom::pcbsys::nirvana::client::nRealmNotFoundException | The specified realm was not found on the server |
| Ccom::pcbsys::nirvana::client::nRealmUnreachableException | Was unable to reach the specified realm |
| Ccom::pcbsys::nirvana::client::nRequestTimedOutException | When the maximum time the client API will wait for a response to a specific request from the Nirvana realm is reached, this exception is thrown |
| Ccom::pcbsys::nirvana::client::nSecurityException | This class defines the security errors that can be thrown by using the nirvana client API |
| Ccom::pcbsys::nirvana::client::nSelectorParserException | The supplied message filter string failed to be parsed |
| Ccom::pcbsys::nirvana::client::nSessionAlreadyInitialisedException | The current nSession has already been initialised |
| Ccom::pcbsys::nirvana::client::nSessionNotConnectedException | The current nSession is not currently connected |
| ►Ccom::pcbsys::nirvana::client::nSessionPausedException | This exception is thrown when an attempt is made by the client to make a request to the server, while the session is paused |
| Ccom::pcbsys::nirvana::client::nPublishPausedException | The currently connected server has been paused, and is not accepting publish requests |
| ►Ccom::pcbsys::nirvana::client::nTransactionException | This class defines the errors that can be thrown by using the nirvana transactional publish API |
| Ccom::pcbsys::nirvana::client::nTransactionAlreadyAbortedException | The transaction has already been aborted and as such is closed |
| Ccom::pcbsys::nirvana::client::nTransactionAlreadyCommittedException | The transaction has already been committed and as such is closed and completed |
| Ccom::pcbsys::nirvana::client::nTransactionIncompleteException | This exception will be thrown if abort or commit is called on a transaction that has not sent any events to the server |
| Ccom::pcbsys::nirvana::client::nTransactionNoEventsException | This exception is thrown if Commit is called on a transaction without any events added in its context |
| Ccom::pcbsys::nirvana::client::nTransactionNoSuchTXIDException | The supplied transaction ID could not be located on server |
| Ccom::pcbsys::nirvana::client::nTransactionNotCommittedException | The transaction has not been committed so the status of the event can not be returned, such as getStartEID or getEndEID |
| Ccom::pcbsys::nirvana::client::nTransactionNotStartedException | The transaction has not been started as such the transaction is not yet established |
| Ccom::pcbsys::nirvana::client::nUnknownTransactionIdException | This exception is thrown when an attempt is made to perform an operation on a transaction where the id of the transaction is not known by the server |
| Ccom::pcbsys::nirvana::client::nUnexpectedResponseException | The server responded with an event that the client did not expect |
| Ccom::pcbsys::nirvana::client::nUnknownRemoteRealmException | The server does not know of the realm that was supplied |
| Ccom::pcbsys::nirvana::client::nUserNotSubscribedException | The user is not currently subscribed to the channel |
| Ccom::pcbsys::nirvana::client::nChannelAttributes | This class is a container for the attributes necessary to create or locate a Nirvana channel or queue |
| Ccom::pcbsys::nirvana::client::nChannelConnectionListener | This interface should be implemented by classes wishing to register to receive callbacks when connections are added or removed to a nirvana channel |
| Ccom::pcbsys::nirvana::client::nChannelIterator | This class iterates synchronously over a Nirvana Realm channel |
| Ccom::pcbsys::nirvana::client::nChannelPublishKeys | This class contains the information about a single channel key |
| Ccom::pcbsys::nirvana::client::nConnectionQueueListener | This interface should be implemented by classes wishing to register to receive asynchronous notifications from the internal connection queue |
| Ccom::pcbsys::nirvana::client::nConstants | This class is a container for the various constants that affect the behaviour of various Nirvana Client API calls |
| ▼Ccom::pcbsys::nirvana::client::nConsumeEvent | This class represents a Nirvana event, which consists of either a tag and some data or an event dictionary and some data |
| Ccom::pcbsys::nirvana::client::nProtobufEvent | This class represents a Google Protocol Buffer Event |
| Ccom::pcbsys::nirvana::client::nConsumeEventFactory | This class is used to facilitate creation of nConsumeEvent objects |
| Ccom::pcbsys::nirvana::client::nCreateResult | This class represents the results of the nSession.create(nChannelAttributes[]) call |
| Ccom::pcbsys::nirvana::client::nDeleteResult | This class represents the results of the nSession.create(nChannelAttributes[]) call |
| Ccom::pcbsys::nirvana::client::nEventAttributes | Used by the nConsumeEvent object in order to store standard header values associated with nirvana client, p2p and JMS events |
| ▼Ccom::pcbsys::nirvana::client::nEventListener | This interface should be implemented by any object that wishes to register itself as an asynchronous subscriber to a nirvana channel or queue |
| Ccom::pcbsys::nirvana::client::nChannelWatcher | This interface extends the nEventListener interface and also provides the ability to receive callbacks for purged events as well as events published on a specific channel or queue |
| Ccom::pcbsys::nirvana::client::nEventProperties | This class contains a collection of key-value pairs, defining event meta data which can be used to create filter rules |
| Ccom::pcbsys::nirvana::client::nEventPropertiesIterator | This class enables you to iterate through the event properties keys and values |
| Ccom::pcbsys::nirvana::client::nFindResult | This class represents the results of the nSession.find(nChannelAttributes[]) call |
| Ccom::pcbsys::nirvana::client::nJoinInformation | This class is a container for all the information that defines a channel join |
| Ccom::pcbsys::nirvana::client::nNamedObject | This class represents a client context on a RealmServer |
| Ccom::pcbsys::nirvana::client::nObject | This class is a holder for different types of object |
| Ccom::pcbsys::nirvana::client::nProtobufEventFactory | This class is used to facilitate creation of nConsumeEvent objects |
| Ccom::pcbsys::nirvana::client::nQueueDetails | Container class, containing statistics on the queue |
| Ccom::pcbsys::nirvana::client::nQueuePeekContext | Provides a context when peeking on the queue |
| ▼Ccom::pcbsys::nirvana::client::nQueueReader | This class is the base class for all Queue Readers and provides a generic reader interface |
| ►Ccom::pcbsys::nirvana::client::nQueueAsyncReader | This Reader enables the client to receive all events asynchronously |
| Ccom::pcbsys::nirvana::client::nQueueAsyncTransactionReader | This Reader enables the client to receive all events asynchronously |
| ►Ccom::pcbsys::nirvana::client::nQueueSyncReader | This class provides the client with a synchronous interface into a Nirvana Queue |
| Ccom::pcbsys::nirvana::client::nQueueSyncTransactionReader | This reader provides a synchronous queue reader model |
| Ccom::pcbsys::nirvana::client::nQueueReaderContext | This class is used to construct a Queue Reader |
| ▼Ccom::pcbsys::nirvana::client::nQueueTransactionReader | Provides the basic interface for transactional queue operations, used by the synchronous and asynchronous transactional queue readers |
| Ccom::pcbsys::nirvana::client::nQueueAsyncTransactionReader | This Reader enables the client to receive all events asynchronously |
| Ccom::pcbsys::nirvana::client::nQueueSyncTransactionReader | This reader provides a synchronous queue reader model |
| Ccom::pcbsys::nirvana::client::nRealm | This class represents a nirvana Realm |
| Ccom::pcbsys::nirvana::client::nReconnectHandler | This interface should be implemented by classes wishing to register to receive callbacks when sessions are disconnected or to take control over the reconnect logic |
| Ccom::pcbsys::nirvana::client::nRegisteredEvent | This class enables a client to maintain a copy of an event, make changes to the properties and then when commit is called only the changes are published to the server |
| Ccom::pcbsys::nirvana::client::nRequestResponseContainer | This class is the container for the request responses |
| Ccom::pcbsys::nirvana::client::nSession | This class represents a Nirvana session, the logical connection between the client API and the Nirvana realm |
| Ccom::pcbsys::nirvana::client::nSessionAttributes | This class is a container for the attributes necessary to create a Nirvana session |
| Ccom::pcbsys::nirvana::client::nSessionFactory | This class is used with a nSessionAttributes object to create a Nirvana session |
| Ccom::pcbsys::nirvana::client::nStoreProperties | Class that contains additional properties that can be set on the channel or queue |
| Ccom::pcbsys::nirvana::client::nSubject | This class contains information about the user identification used by Nirvana |
| Ccom::pcbsys::nirvana::client::nSubscriptionAttributes | This class represents the attributes used for channel subscriptions |
| Ccom::pcbsys::nirvana::client::nTransaction | This class enables the client to perform transactional publishing, representing a nirvana transaction |
| Ccom::pcbsys::nirvana::client::nTransactionAttributes | This class is a container for the attributes necessary to create a Nirvana transaction |
| Ccom::pcbsys::nirvana::client::nTransactionFactory | This class is used with a nTransactionAttributes object to create a Nirvana transaction |
| Ccom::softwareag::umtransport::AcceptHandler | This interface is passed to TransportFactory.bind when you want to create an AsynchronousServerTransport. The onAccept method will be invoked whenever a client connected to the ServerTransport |
| Ccom::softwareag::umtransport::ClientTransportContextFactory | This factory allows you to construct ClientTransportContexts by passing a String URL. This way you can compile an application which is Transport agnostic and simply change the URL passed to the application to switch from SHM to Sockets etc. A URL is of the form protocol://host:port?Property=value&Property2=value2 The relevant ClientContextBuilder will be constructed based on the protocol and then the properties will be set internally. So on a ClientSHMTransportContext there is a property called "LowLatency" that you could set to true using a URL like this: |
| Ccom::softwareag::umtransport::CloseHandler | The CloseHandler interface is passed to the TransportFactory.bind method when you want to create and AsynchronousServerTransport or to the TransportFactory.connect method when you want to create client side AsynchronousTransports. The object which implements this interface will be notified when Transports are closed |
| Ccom::softwareag::umtransport::ConnectHandler | This interface is passed to TransportFactory.connect when you want to create an AsynchronousTransport. The onConnect method will be called when the Transport connects |
| ▼Ccom::softwareag::umtransport::ContextBuilder | Represents a Builder object which is used to create client or server TransportContexts |
| ►Ccom::softwareag::umtransport::ClientContextBuilder | This is an abstract Builder object which is used to create client side Transports |
| Ccom::softwareag::umtransport::ClientRDMATransportContext::Builder | This Builder object is used to build a ClientRDMATransportContext. The ClientRDMATransportContext is configured using the builder so that once build() is called, the ClientRDMATransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| Ccom::softwareag::umtransport::ClientSHMTransportContext::Builder | This Builder object is used to build a ClientSHMTransportContext. The ClientSHMTransportContext is configured using the builder so that once build() is called, the ClientSHMTransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| ►Ccom::softwareag::umtransport::ClientSocketTransportContext::Builder | This Builder object is used to build a ClientSocketTransportContext. The ClientSocketTransportContext is configured using the builder so that once build() is called, the ClientSocketTransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| Ccom::softwareag::umtransport::ClientSSLTransportContext::Builder | This Builder object is used to build a ClientSSLTransportContext. The ClientSSLTransportContext is configured using the builder so that once build() is called, the ClientSocketTransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| ►Ccom::softwareag::umtransport::ServerContextBuilder | This is an abstract builder object that is used to create ServerTransports |
| Ccom::softwareag::umtransport::ServerRDMATransportContext::Builder | This Builder object is used to build a ServerRDMATransportContext. The ServerRDMATransportContext is configured using the builder so that once build() is called, the ServerRDMATransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| Ccom::softwareag::umtransport::ServerSHMTransportContext::Builder | This Builder object is used to build a ServerSHMTransportContext. The ServerSHMTransportContext is configured using the builder so that once build() is called, the ServerSHMTransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| ►Ccom::softwareag::umtransport::ServerSocketTransportContext::Builder | This Builder object is used to build a ServerSocketTransportContext. The ServerSocketTransportContext is configured using the builder so that once build() is called, the ServerSocketTransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| Ccom::softwareag::umtransport::ServerSSLTransportContext::Builder | This Builder object is used to build a ServerSSLTransportContext. The ServerSSLTransportContext is configured using the builder so that once build() is called, the ServerSSLTransportContext is only returned if it is valid. You can use the Builder to create simple readable code like this: |
| Ccom::softwareag::umtransport::DataHandler | This interface is passed to the TransportFactory.connect method when you want to create an AsynchronousTransport. It is also passed to the TransportFactory.bind method when you want an AsynchronousServerTransport. The onRead method will be called when data has been read from the AsynchronousTransport |
| Ccom::softwareag::umtransport::Logger | The class used to log messages in UM Transport |
| Ccom::softwareag::umtransport::LogListener | This class provides a mechanism to override the default Logging within the umTransport code. This allows users to then log messaging using any log mechanism they want to use |
| ▼Ccom::softwareag::umtransport::ServerTransport | Interface that defines methods common to all ServerTransports |
| Ccom::softwareag::umtransport::AsynchronousServerTransport | By establishing an AsynchronousServerTransport, new client connections will automatically be accepted and notifications of new connections will be passed to the user implementation of AcceptHandler. To create an AsynchronousServerTransport you must first create a ServerTransportContext and then pass this to the TransportFactory.bind method with the required callback objects (AcceptHandler, DataHandler, CloseHandler) |
| Ccom::softwareag::umtransport::SynchronousServerTransport | This ServerTransport is used synchronously accept client transports. The accept() call is a blocking call which will return a SynchronousTransport as soon as it connects |
| ▼Ccom::softwareag::umtransport::Transport | Interface that defines methods common to all client Transports |
| Ccom::softwareag::umtransport::AsynchronousTransport | This is a client side Transport object. It is constructed on the client side by creating a ClientTransportContext which is then passed to TransportFactory.bind with the required callback objects (DataHandler, CloseHandler). On the server side, an AsynchronousServerTransport will accept connections and handle them as AsynchronousTransports |
| Ccom::softwareag::umtransport::SynchronousTransport | This Transport represents a client connection. It is created on the client side using TransportFactory.connect and on the server side using SynchronousServerTransport.accept(). Read and write calls to this Transport are blocking calls |
| ▼Ccom::softwareag::umtransport::TransportContext | Abstract class that defines methods common to all TransportContexts |
| ►Ccom::softwareag::umtransport::ClientTransportContext | This represents a client side TransportContect that is used to create Transport objects using the TransportFactory |
| Ccom::softwareag::umtransport::ClientRDMATransportContext | Constructed using the ClientRDMATransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport is transmitted using Remote Direct Memory Access |
| Ccom::softwareag::umtransport::ClientSHMTransportContext | Constructed using the ClientSHMTransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport is transmitted using Shared Memory |
| ►Ccom::softwareag::umtransport::ClientSocketTransportContext | Constructed using the ClientSocketTransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport is transmitted using TCP Sockets |
| Ccom::softwareag::umtransport::ClientSSLTransportContext | Constructed using the ClientSSLTransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport is encrypted using SSL and transmitted using Sockets |
| ►Ccom::softwareag::umtransport::ServerTransportContext | Abstract class which defines methods common to all ServerTransportContexts |
| Ccom::softwareag::umtransport::ServerRDMATransportContext | Constructed using the ServerRDMATransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.bind. Communication on the transport is transmitted using Remote Direct Memory Access |
| Ccom::softwareag::umtransport::ServerSHMTransportContext | Constructed using the ServerSHMTransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport is transmitted using Shared Memory |
| ►Ccom::softwareag::umtransport::ServerSocketTransportContext | Constructed using the ServerSocketTransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport is transmitted using TCP Sockets |
| Ccom::softwareag::umtransport::ServerSSLTransportContext | Constructed using the ServerSSLTransportContext.Builder. All information must be set on the Builder so that when this object is built, it is validated. It is used to create Transport objects using TransportFactory.connect. Communication on the transport SSL encrypted and transmitted using Sockets |
| Ccom::softwareag::umtransport::TransportFactory | The TransportFactory is used to to create ServerTransports or client Transports. To bind a server Transport you need to first create a ServerTransportContext or to connect to an existing server you need to create a ClientTransportContext |
