O'Reilly - Java Message Service

A.3 Publish-and-Subscribe API
This section covers the topic-based API.
A.3.1 TemporaryTopic
Java Message Service
A TemporaryTopic is created by a TopicSession. A temporary topic is associated with the
connection that belongs to the TopicSession that created it. It is only active for the duration
of the session's connection, and it is guaranteed to be unique across all connections. Since
it is temporary it can't be durable - it lasts only as long as its associated client connection is
active. In all other respects it is just like a "regular" topic. The TemporaryTopic is a subtype
of the Topic interface.
Since a temporary topic is created by a JMS client, it is unavailable to other JMS clients
unless the topic identity is transferred using the JMSReplyTo header. While any client may
publish messages on another client's temporary topic, only the sessions that are associated
with the JMS client connection that created the temporary topic may subscribe to it. JMS
clients can also, of course, publish messages to their own temporary topics:
public interface TemporaryTopic extends Topic {
public void delete( ) throws JMSException;
}
A.3.2 Topic
The Topic is an administered object that acts as a handle or identifier for an actual topic,
called a physical topic, on the messaging server. A physical topic is a channel to which
many clients can subscribe and publish. When a JMS client delivers a Message object to a
topic, all the clients subscribed to that topic receive the Message. The Topic is a subtype of
the Destination interface:
public interface Topic extends Destination {
public String getTopicName( ) throws JMSException;
public String toString( );
}
A.3.3 TopicConnection
The TopicConnection is created by the TopicConnectionFactory. The TopicConnection
represents a connection to the message server. Each TopicConnection created from a
TopicConnectionFactory is a unique connection to the server. [B] The TopicConnection is a
subtype of the Connection interface:
[B] The actual physical network connection may or may not be unique, depending on the vendor.
However, the connection is considered to be logically unique so authentication and connection
control can be managed separately from other connections.
public interface TopicConnection extends Connection {
public TopicSession createTopicSession(boolean transacted,
int acknowledgeMode)
throws JMSException;
public ConnectionConsumer createConnectionConsumer
(Topic topic, String messageSelector,
ServerSessionPool sessionPool,
int maxMessages)
153