All Classes and Interfaces
Class
Description
A
BytesMessage object is used to send a message containing a
stream of uninterpreted bytes.A
Connection object is a client's active connection to its JMS
provider.For application servers,
Connection objects provide a special
facility
for creating a ConnectionConsumer (optional).A
ConnectionFactory object encapsulates a set of connection
configuration
parameters that has been defined by an administrator.A
ConnectionMetaData object provides information describing the
Connection object.The delivery modes supported by the JMS API are
PERSISTENT and
NON_PERSISTENT.A
Destination object encapsulates a provider-specific
address.If a JMS provider detects a serious problem with a
Connection
object, it informs the Connection object's
ExceptionListener, if one has been registered. This exception is thrown when a method is
invoked at an illegal or inappropriate time or if the provider is
not in an appropriate state for the requested operation.
This exception must be thrown when a
client attempts to set a connection's client ID to a value that
is rejected by a provider.
This exception must be thrown when a
destination either is not understood by a provider or is no
longer valid.
This exception must be thrown when a
JMS client attempts to give a provider a message selector with
invalid syntax.
This is the root class of all JMS API exceptions.
This exception must be thrown when a provider rejects a user
name/password submitted by a client.
A
MapMessage object is used to send a set of name-value pairs.The
Message interface is the root interface of all JMS
messages.A client uses a
MessageConsumer object to receive messages
from a destination. This exception must be thrown when an unexpected
end of stream has been reached when a
StreamMessage or
BytesMessage is being read. This exception must be thrown when a JMS client
attempts to use a data type not supported by a message or attempts to
read data in a message as the wrong type.
A
MessageListener object is used to receive asynchronously
delivered messages. This exception must be thrown when a JMS client attempts to read a
write-only message.
This exception must be thrown when a JMS client attempts to write to a
read-only message.
A client uses a
MessageProducer object to send messages to a
destination.An
ObjectMessage object is used to send a message that contains
a serializable object in the Java programming language ("Java object").A
Queue object encapsulates a provider-specific queue name.A client uses a
QueueBrowser object to look at messages on a
queue without removing them.A
QueueConnection object is an active connection to a
point-to-point JMS provider.A client uses a
QueueConnectionFactory object to create
QueueConnection objects with a point-to-point JMS provider.A client uses a
QueueReceiver object to receive messages that
have been delivered to a queue.A queue requestor
A client uses a
QueueSender object to send messages to a queue.A
QueueSession object provides methods for creating
QueueReceiver, QueueSender,
QueueBrowser, and TemporaryQueue objects.This exception is thrown when a provider is unable to allocate the
resources required by a method.
A
ServerSession object is an application server object that
is used by a server to associate a thread with a JMS session (optional).A
ServerSessionPool object is an object implemented by an
application server to provide a pool of ServerSession objects
for processing the messages of a ConnectionConsumer (optional).A
Session object is a single-threaded context for producing and consuming
messages.A
StreamMessage object is used to send a stream of primitive
types in the Java programming language.A
TemporaryQueue object is a unique Queue object
created for the duration of a Connection.A
TemporaryTopic object is a unique Topic object
created for the duration of a Connection.A
TextMessage object is used to send a message containing a
java.lang.String.A
Topic object encapsulates a provider-specific topic name.A
TopicConnection object is an active connection to a
publish/subscribe JMS provider.A client uses a
TopicConnectionFactory object to create
TopicConnection objects with a publish/subscribe JMS provider.A client uses a
TopicPublisher object to publish messages on a
topic.Provides a basic request/reply layer ontop of JMS.
A
TopicSession object provides methods for creating
TopicPublisher, TopicSubscriber, and
TemporaryTopic objects.A client uses a
TopicSubscriber object to receive messages that
have been published to a topic. This exception is thrown when an
operation is invalid because a transaction is in progress.
This exception must be thrown when a
call to
Session.commit results in a rollback of the current
transaction.The
XAConnection interface extends the capability of
Connection by providing an XASession (optional).The
XAConnectionFactory interface is a base interface for the
XAQueueConnectionFactory and
XATopicConnectionFactory interfaces.An
XAQueueConnection provides the same create options as
QueueConnection (optional).An
XAQueueConnectionFactory provides the same create options as
a QueueConnectionFactory (optional).An
XAQueueSession provides a regular QueueSession,
which can be used to
create QueueReceiver, QueueSender, and
QueueBrowser objects (optional).The
XASession interface extends the capability of
Session by adding access to a JMS provider's support for the
Java Transaction API (JTA) (optional).An
XATopicConnection provides the same create options as
TopicConnection (optional).An
XATopicConnectionFactory provides the same create options as
a TopicConnectionFactory (optional).An
XATopicSession provides a regular TopicSession.