cms-1.2 Data Structures

Here are the data structures with brief descriptions:
cms::BytesMessageA message used for sending a stream of uninterpreted bytes
cms::CloseableInterface for a class that implements the close method
cms::CMSExceptionThis class represents an error that has occurred in cms
cms::CMSPropertiesInterface for a Java-like properties object
cms::ConnectionThe client's connection to its provider
cms::ConnectionFactoryDefines the interface for a factory that creates connection objects
cms::DeliveryModeThis is an Abstract class whose purpose is to provide a container for the delivery mode enumeration for CMS messages
cms::DestinationA Destination object encapsulates a provider-specific address
cms::ExceptionListenerIf a CMS provider detects a serious problem, it notifies the client application through an ExceptionListener that is registered with the Connection
cms::MapMessageA MapMessage object is used to send a set of name-value pairs
cms::MessageRoot of all messages
cms::MessageConsumerA client uses a MessageConsumer to received messages from a destination
cms::MessageListenerA MessageListener object is used to receive asynchronously delivered messages
cms::MessageProducerA client uses a MessageProducer object to send messages to a destination
cms::ObjectMessagePlace holder for interaction with JMS systems that support Java serialized ObjectMessages
cms::QueueAn interface encapsulating a provider-specific queue name
cms::SessionA Session object is a single-threaded context for producing and consuming messages
cms::StartableInterface for a class that implements the start method
cms::StoppableInterface for a class that implements the stop method
cms::TemporaryQueueAn interface encapsulating a provider-specific queue name
cms::TemporaryTopicAn interface encapsulating a provider-specific topic name
cms::TextMessageInterface for a text message
cms::TopicAn interface encapsulating a provider-specific topic name

Generated on Sat Oct 27 16:56:58 2007 for cms-1.2 by  doxygen 1.5.3