# Functions
CreateJMSException is a helper function for creating a JMSException.
No description provided by the author
# Constants
DeliveryMode_NON_PERSISTENT is Used to configure messages to be sent Non-Persistently.
DeliveryMode_PERSISTENT is used to configure messages to be sent Persistently.
Destination_PUT_ASYNC_ALLOWED_AS_DEST allows the async message behaviour to be controlled by the queue on the queue manager.
Destination_PUT_ASYNC_ALLOWED_DISABLED is used to disable messages being sent asynchronously.
Destination_PUT_ASYNC_ALLOWED_ENABLED is used to enable messages being sent asynchronously.
JMSContextAUTOACKNOWLEDGE is used to specify a sessionMode that automatically acknowledge message transmission.
JMSContextSESSIONTRANSACTED is used to specify a sessionMode that requires manual commit/rollback of transactions.
Priority_DEFAULT is the default priority for messages sent using a Producer.
# Structs
JMSExceptionImpl is a struct that implements the JMSException interface.
# Interfaces
BytesMessage is used to send a message containing a slice of bytes
Instances of this object are created using the functions on the JMSContext such as CreateBytesMessage and CreateBytesMessageWithBytes.
ConnectionFactory defines a Golang interface which provides similar functionality as the Java JMS ConnectionFactory - encapsulating a set of connection configuration parameters that allows an application to create connections to a messaging provider.
Destination encapsulates a provider-specific address, which is typically specialized as either a Queue or a Topic.
JMSConsumer provides the ability for an application to receive messages from a queue or a topic.
JMSContext represents a connection to the messaging provider, and provides the capability for applications to create Producer and Consumer objects so that it can send and receive messages.
JMSException represents an interface for returning details of a condition that has caused a function call to fail.
JMSProducer is a simple object used to send messages on behalf of a JMSContext.
Message is the root interface of all JMS Messages.
MessageIterator provides the ability for the application to consume a sequence of Messages.
Queue encapsulates a provider-specific queue name through which an application can carry out point to point messaging.
QueueBrowser provides the ability for an application to look at messages on a queue without removing them.
TextMessage is used to send a message containing a string.
# Type aliases
No description provided by the author