All Implemented Interfaces:
Session
QueueSession object provides methods for creating
QueueReceiver, QueueSender,
QueueBrowser, and TemporaryQueue objects.
If there are messages that have been received but not acknowledged
when a QueueSession terminates, these messages will be retained
and redelivered when a consumer next accesses the queue.
A QueueSession is used for creating Point-to-Point specific
objects. In general, use the Session object.
The QueueSession is used to support
existing code. Using the Session object simplifies the
programming model, and allows transactions to be used across the two
messaging domains.
A QueueSession cannot be used to create objects specific to the
publish/subscribe domain. The following methods inherit from
Session, but must throw an
IllegalStateException
if they are used from QueueSession:
createDurableSubscriber
createTemporaryTopic
createTopic
unsubscribe
| Method from javax.jms.QueueSession Summary: |
|---|
| createBrowser, createBrowser, createQueue, createReceiver, createReceiver, createSender, createTemporaryQueue |
| Method from javax.jms.QueueSession Detail: |
|---|
QueueBrowser object to peek at the messages on
the specified queue. |
QueueBrowser object to peek at the messages on
the specified queue using a message selector. |
Queue name.
This facility is provided for the rare cases where clients need to dynamically manipulate queue identity. It allows the creation of a queue identity with a provider-specific name. Clients that depend on this ability are not portable. Note that this method is not for creating the physical queue.
The physical creation of queues is an administrative task and is not
to be initiated by the JMS API. The one exception is the
creation of temporary queues, which is accomplished with the
|
QueueReceiver object to receive messages from the
specified queue. |
QueueReceiver object to receive messages from the
specified queue using a message selector. |
QueueSender object to send messages to the
specified queue. |
TemporaryQueue object. Its lifetime will be that
of the QueueConnection unless it is deleted earlier. |