Package org.apache.activemq
package org.apache.activemq
The core JMS client API implementation classes.
-
ClassDescriptionFor application servers,
Connection
objects provide a special facility for creating aConnectionConsumer
(optional).A ConnectionFactory is an an Administered object, and is used for creating Connections.AConnectionMetaData
object provides information describing theConnection
object.In terms of the JMS 1.1 API a JMSContext should be thought of as representing both a Connection and a Session.Provides basic audit functions for MessagesProvides basic audit functions for Messages without syncA client uses aMessageConsumer
object to receive messages from a destination.A client uses aMessageProducer
object to send messages to a destination.A useful base class for implementing aMessageProducer
A helper class for converting normal JMS interfaces into ActiveMQ specific ones.Defines the prefetch message policies for different types of consumersA client uses aQueueBrowser
object to look at messages on a queue without removing them.A client uses aQueueReceiver
object to receive messages that have been delivered to a queue.A client uses aQueueSender
object to send messages to a queue.A QueueSession implementation that throws IllegalStateExceptions when Topic operations are attempted but which delegates to another QueueSession for all other operations.ASession
object is a single-threaded context for producing and consuming messages.A utility class used by the Session for dispatching messages asynchronously to consumersAn ActiveMQConnectionFactory that allows access to the key and trust managers used for SslConnections.A client uses aTopicPublisher
object to publish messages on a topic.A TopicSession implementation that throws IllegalStateExceptions when Queue operations are attempted but which delegates to another TopicSession for all other operations.A client uses aTopicSubscriber
object to receive messages that have been published to a topic.The XAConnection interface extends the capability of Connection by providing an XASession (optional).A factory ofXAConnection
instancesThe XASession interface extends the capability of Session by adding access to a JMS provider's support for the Java Transaction API (JTA) (optional).An exception which is closed if you try to access a resource which has already been closedRepresents a message which has a typically out of band Binary Large Object (BLOB)An exception listener similar to the standardjakarta.jms.ExceptionListener
which can be used by client code to be notified of exceptions thrown by container components (e.g. an EJB container in case of Message Driven Beans) during asynchronous processing of a message.Provides a uniform interface that can be used to close all the JMS obejcts that provide a close() method.An exception thrown when a service is not correctly configuredAn exception thrown when attempt is made to use a connection when the connection has been closed.An exception thrown when the a connection failure is detected (peer might close the connection, or a keep alive times out, etc.)Represents a hook to allow the support of custom destinations such as to support Apache Camel to create and manage endpointsAn exception thrown on a send if a destination does not exist.A set of enhanced APIs for a JMS providerAn exception thrown when max frame size is exceeded.Represents the JMS extension methods in Apache ActiveMQAn extended JMS interface that adds the ability to be notified when a message is available for consumption using the receive*() methods which is useful in Ajax style subscription models.A listener which is notified if a message is available for processing via the receive methods.A plugin strategy for transforming a message before it is sent by the JMS client or before it is dispatched to the JMS consumerA useful base class for message transformers.An exception thrown when an operation is invoked on a service which has not yet been started.Configuration options for a messageConsumer used to control how messages are re-delivered when they are rolled back.The core lifecyle interface for ActiveMQ components.A holder for different thread priorites used in ActiveMQA TransactionContext provides the means to control a JMS transaction.