All Classes and Interfaces
Class
Description
Specifies the different possible modes of acknowledgment:
In ACK_AUTO mode, every time the user receives a message, it is
acknowledged automatically.
This is a JMS Wrapper of
SqsClient.Used by session to automatically acknowledge a client's receipt of a message
either when the session has successfully returned from a call to receive or
when the message listener the session has called to process the message
successfully returns.
This is used by different acknowledgers that requires partitioning of the
list, and execute actions on the partitions
Simple exponential back-off strategy, that is used for re-tries on SQS
interactions.
Used to negative acknowledge of group of messages.
This interface is helper to notify when the prefetchThread should be resuming
messages.
Used to acknowledge group of messages.
This class borrows from
ActiveMQStreamMessage, which is also
licensed under Apache2.0.This is a logical connection entity, which encapsulates the logic to create
sessions.
A ConnectionFactory object encapsulates a set of connection configuration
parameters for
SqsClient as well as setting
numberOfMessagesToPrefetch.The SQSMessage is the root class of all SQS JMS messages and implements JMS
Message interface.
This class is used fulfill object value, corresponding SQS message
attribute type and message attribute string value.
Copied from org.apache.activemq.util.TypeConversionSupport to provide the
same property support provided by activemq without creating a dependency
on activemq.
A client uses a MessageConsumer object to receive messages from a
destination.
Used internally to prefetch messages to internal buffer on a background
thread for better
receive turn around times.Identifies an SQS message, when (negative)acknowledging the message
A client uses a MessageProducer object to send messages to a queue
destination.
Simple thread factory that supports ThreadGroups
Includes utility classes to use when serializing property names to SQS
message attribute names.
An ObjectMessage object is used to send a message that contains a Java
serializable object.
A SQSQueueDestination object encapsulates a queue name and SQS specific queue
URL.
A session serves several purposes:
It is a factory for its message producers and consumers.
It provides a way to create Queue objects for those clients that need to
dynamically manipulate provider-specific destination names.
It retains messages it consumes until they have been acknowledged.
It serializes execution of message listeners registered with its message
consumers.
Used internally to guarantee serial execution of message processing on
consumer message listeners.
A TextMessage object is used to send a message body containing a
java.lang.String.
Used to acknowledge messages in any order one at a time.