All Downloads are FREE. Search and download functionalities are using the official Maven repository.

javax.jms.TopicSubscriber Maven / Gradle / Ivy

Go to download

This artifact provides a single jar that contains all classes required to use remote EJB and JMS, including all dependencies. It is intended for use by those not using maven, maven users should just import the EJB and JMS BOM's instead (shaded JAR's cause lots of problems with maven, as it is very easy to inadvertently end up with different versions on classes on the class path).

There is a newer version: 34.0.0.Final
Show newest version
/*
 * Copyright (c) 1997, 2017 Oracle and/or its affiliates. All rights reserved.
 *
 * This program and the accompanying materials are made available under the
 * terms of the Eclipse Public License v. 2.0, which is available at
 * http://www.eclipse.org/legal/epl-2.0.
 *
 * This Source Code may also be made available under the following Secondary
 * Licenses when the conditions for such availability set forth in the
 * Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
 * version 2 with the GNU Classpath Exception, which is available at
 * https://www.gnu.org/software/classpath/license.html.
 *
 * SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
 */

package javax.jms;

/**
 * A client uses a {@code TopicSubscriber} object to receive messages that have been published to a topic. A
 * {@code TopicSubscriber} object is the publish/subscribe form of a message consumer. A {@code MessageConsumer} can be
 * created by using {@code Session.createConsumer}.
 *
 * 

* A {@code TopicSession} allows the creation of multiple {@code TopicSubscriber} objects per topic. It will deliver * each message for a topic to each subscriber eligible to receive it. Each copy of the message is treated as a * completely separate message. Work done on one copy has no effect on the others; acknowledging one does not * acknowledge the others; one message may be delivered immediately, while another waits for its subscriber to process * messages ahead of it. * *

* Regular {@code TopicSubscriber} objects are not durable. They receive only messages that are published while they are * active. * *

* Messages filtered out by a subscriber's message selector will never be delivered to the subscriber. From the * subscriber's perspective, they do not exist. * *

* In some cases, a connection may both publish and subscribe to a topic. The subscriber {@code NoLocal} attribute * allows a subscriber to inhibit the delivery of messages published by its own connection. * *

* If a client needs to receive all the messages published on a topic, including the ones published while the subscriber * is inactive, it uses a durable {@code TopicSubscriber}. The Jakarta Messaging provider retains a record of this durable * subscription and insures that all messages from the topic's publishers are retained until they are acknowledged by * this durable subscriber or they have expired. * *

* Sessions with durable subscribers must always provide the same client identifier. In addition, each client must * specify a name that uniquely identifies (within client identifier) each durable subscription it creates. Only one * session at a time can have a {@code TopicSubscriber} for a particular durable subscription. * *

* A client can change an existing durable subscription by creating a durable {@code TopicSubscriber} with the same name * and a new topic and/or message selector. Changing a durable subscription is equivalent to unsubscribing (deleting) * the old one and creating a new one. * *

* The {@code unsubscribe} method is used to delete a durable subscription. The {@code unsubscribe} method can be used * at the {@code Session} or {@code TopicSession} level. This method deletes the state being maintained on behalf of the * subscriber by its provider. * *

* Creating a {@code MessageConsumer} provides the same features as creating a {@code TopicSubscriber}. To create a * durable subscriber, use of {@code Session.CreateDurableSubscriber} is recommended. The {@code TopicSubscriber} is * provided to support existing code. * * @see javax.jms.Session#createConsumer * @see javax.jms.Session#createDurableSubscriber * @see javax.jms.TopicSession * @see javax.jms.TopicSession#createSubscriber * @see javax.jms.MessageConsumer * * @version Jakarta Messaging 2.0 * @since JMS 1.0 */ public interface TopicSubscriber extends MessageConsumer { /** * Gets the {@code Topic} associated with this subscriber. * * @return this subscriber's {@code Topic} * * @exception JMSException if the Jakarta Messaging provider fails to get the topic for this topic subscriber due to some internal * error. */ Topic getTopic() throws JMSException; /** * Gets the {@code NoLocal} attribute for this subscriber. The default value for this attribute is false. * * @return true if locally published messages are being inhibited * * @exception JMSException if the Jakarta Messaging provider fails to get the {@code NoLocal} attribute for this topic subscriber due * to some internal error. */ boolean getNoLocal() throws JMSException; }





© 2015 - 2024 Weber Informatics LLC | Privacy Policy