com.microsoft.azure.servicebus

Classes

ClientFactory

Utility class for creating message senders and receivers.

ClientSettings

Class encapsulating common client level settings like TokenProvider, RetryPolicy, OperationTimeout.

Message
MessageBody

This class encapsulates the body of a message. Body types map to AMQP message body types. It has getters and setters for multiple body types. Client should test for body type before calling corresponding get method. Get methods not corresponding to the type of the body return null.

MessageHandlerOptions

The OnMessage handler processing options.

MessageSession
QueueClient
SessionHandlerOptions

The OnSession handler processing options.

SubscriptionClient
TopicClient

The topic client that interacts with service bus topic.

TransactionContext

Represents an active servicebus transaction. A transaction is initiated by calling startTransactionAsync(). A transaction can result in commit or rollback. To commit, call endTransactionAsync(TransactionContext transaction, boolean commit) with To rollback, call endTransactionAsync(TransactionContext transaction, boolean commit) with

Utils

Interfaces

ICloseable

Defines a standard way of properly closing and disposing objects.

IMessage

Represents the message that is exchanged between Azure Service Bus and its clients.

IMessageBrowser

Represents a message browser that can browse messages from Azure Service Bus.

IMessageEntityClient

Represents a messaging client to an Azure Service Bus entity.

IMessageHandler

Defines the contract for registering the callback QueueClient#registerMessageHandler(IMessageHandler) and SubscriptionClient#registerMessageHandler(IMessageHandler) for QueueClient and SubscriptionClient.

IMessageReceiver

Defines message receiver interface. The MessageReceiver can be used to receive messages from Queues and Subscriptions and acknowledge them.

IMessageSender

Represents a message sender that sends messages to Azure Service Bus.

IMessageSession

Describes a Session object. IMessageSession can be used to perform operations on sessions.

Service Bus Sessions, also called 'Groups' in the AMQP 1.0 protocol, are unbounded sequences of related messages. ServiceBus guarantees ordering of messages in a session.

Any sender can create a session when submitting messages into a Topic or Queue by setting the Message#sessionId property on Message to some application defined unique identifier. At the AMQP 1.0 protocol level, this value maps to the group-id property.

Sessions come into existence when there is at least one message with the session's SessionId in the Queue or Topic subscription. Once a Session exists, there is no defined moment or gesture for when the session expires or disappears.

IMessageSessionEntity

Represents a session full client entity.

IQueueClient

QueueClient can be used for all basic interactions with a Service Bus Queue.

ISessionHandler

Defines the contract for registering the session message processing callback QueueClient#registerSessionHandler(ISessionHandler) or SubscriptionClient#registerSessionHandler(ISessionHandler) for QueueClient and SubscriptionClient.

ISubscriptionClient

SubscriptionClient can be used for all basic interactions with a Service Bus Subscription.

ITopicClient

TopicClient can be used for all basic interactions with a Service Bus topic.

Enums

ExceptionPhase

Enumeration to represent the phase in a message pump or session pump at which an exception occurred.

MessageBodyType

Enumeration to represent body type of a message.

ReceiveMode

Enumeration to represent the two receive modes Azure Service Bus supports.