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 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. 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.
This exception is thrown when a provider is unable to allocate the resources required by a method. 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. A BytesMessage object is used to send a message containing a stream of uninterpreted bytes. A Destination object encapsulates a provider-specific address.
A MapMessage object is used to send a set of name-value pairs. Although these remain part of JMS for reasons of backwards compatibility they should be considered to be completely superseded by the later APIs. JMS 1. This is referred to here as the classic API. JMS 2. Each API offers a different set of interfaces for connecting to a JMS provider and for sending and receiving messages.
However they all share a common set of interfaces for representing messages and message destinations and to provide various utility features. All interfaces are in the javax.
This interface is also used by the simplified API. Connection - an active connection to a JMS provider Session - a single-threaded context for sending and receiving messages MessageProducer - an object created by a Session that is used for sending messages to a queue or topic MessageConsumer - an object created by a Session that is used for receiving messages sent to a queue or topic Simplified API interfaces The simplified API provides the same messaging functionality as the classic API but requires fewer interfaces and is simpler to use.
This interface is also used by the classic API. The main interfaces provided by the domain-specific API for point-to-point messaging are as follows: QueueConnectionFactory - an administered object used by a client to create a QueueConnection. TopicConnection - an active connection to a JMS provider TopicSession - a single-threaded context for sending and receiving messages TopicPublisher - an object created by a TopicSession that is used for sending messages to a topic TopicSubscriber - an object created by a TopicSession that is used for receiving messages sent to a topic Terminology for sending and receiving messages The term consume is used in this document to mean the receipt of a message by a JMS client; that is, a JMS provider has received a message and has given it to its client.
Since JMS supports both synchronous and asynchronous receipt of messages, the term consume is used when there is no need to make a distinction between them. The term produce is used as the most general term for sending a message. It means giving a message to a JMS provider for delivery to a destination.
A JMS application can be architected and deployed as a unit. In many cases, JMS clients are added incrementally to an existing application. The message definitions used by an application may originate with JMS, or they may have been defined by the non-JMS part of the application. Delivery of message is started automatically At this point a client has the basic JMS setup needed to produce and consume messages.
Package Specification Java Message Service 2. All Rights Reserved. Use is subject to license terms. Skip navigation links. Package javax. A CompletionListener is implemented by the application and may be specified when a message is sent asynchronously.
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.
A client uses a QueueBrowser object to look at messages on a queue without removing them. A client uses a QueueReceiver object to receive messages that have been delivered to a queue. 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. A client uses a TopicPublisher object to publish messages on a topic. A client uses a TopicSubscriber object to receive messages that have been published to a topic. BytesMessage A BytesMessage object is used to send a message containing a stream of uninterpreted bytes. CompletionListener A CompletionListener is implemented by the application and may be specified when a message is sent asynchronously.
ConnectionConsumer For application servers, Connection objects provide a special facility for creating a ConnectionConsumer optional. ConnectionFactory A ConnectionFactory object encapsulates a set of connection configuration parameters that has been defined by an administrator.
Destination A Destination object encapsulates a provider-specific address.
0コメント