javax.jms

Interface Queue

  • All Superinterfaces:
    Destination
    All Known Subinterfaces:
    TemporaryQueue

    public interface Queue
    extends Destination
    A Queue object encapsulates a provider-specific queue name. It is the way a client specifies the identity of a queue to JMS API methods. For those methods that use a Destination as a parameter, a Queue object used as an argument. For example, a queue can be used to create a MessageConsumer and a MessageProducer by calling:
    • Session.CreateConsumer(Destination destination)
    • Session.CreateProducer(Destination destination)

    The actual length of time messages are held by a queue and the consequences of resource overflow are not defined by the JMS API.

    Since:
    JMS 1.0
    Version:
    JMS 2.0
    See Also:
    Session.createConsumer(Destination), Session.createProducer(Destination), Session.createQueue(String), QueueSession.createQueue(String)
    • Method Detail

      • getQueueName

        String getQueueName()
                     throws JMSException
        Gets the name of this queue.

        Clients that depend upon the name are not portable.

        Returns:
        the queue name
        Throws:
        JMSException - if the JMS provider implementation of Queue fails to return the queue name due to some internal error.
      • toString

        String toString()
        Returns a string representation of this object.
        Overrides:
        toString in class Object
        Returns:
        the provider-specific identity values for this queue

Document created the 11/06/2005, last modified the 18/08/2025
Source of the printed document:https://www.gaudry.be/en/java-api-javaee-rf-javax/jms/Queue.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com, Queue (Java(TM) EE 7 Specification APIs)

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author of this site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.