Skip navigation links

Package oracle.jdbc.aq

This package is an Oracle JDBC extension that provides interfaces to access the Advanced Queuing feature of Oracle for enterprise messaging applications.

See:
Description

Interface Summary

AQAgent	An Agent represents and identifies a user of the queue, either producer or consumer of the message, either an end-user or an application.
AQMessage	A message is the unit that is enqueued or dequeued.
AQMessageProperties	This interface contains the message properties such as Correlation, Sender, Delay and Expiration, Recipients, and Priority and Ordering.
AQNotificationListener	The listener interface for receiving AQ notification events.
AQNotificationRegistration	This class represents your interest in being notified when a new message is enqueued in a particular queue.

Class Summary

AQDequeueOptions	Specifies the options available for the dequeue operation.
AQEnqueueOptions	Specifies the options available for the enqueue operation.
AQFactory	Factory class for AQ.
AQNotificationEvent	An AQNotificationEvent will be created whenever a new message is enqueued in a queue for which you have registered your interest (see OracleConnection.registerAQNotification).

Enum Summary

AQDequeueOptions.DeliveryFilter
AQDequeueOptions.DequeueMode
AQDequeueOptions.NavigationOption
AQDequeueOptions.VisibilityOption
AQEnqueueOptions.DeliveryMode
AQEnqueueOptions.SequenceDeviationOption
AQEnqueueOptions.VisibilityOption
AQMessageProperties.DeliveryMode
AQMessageProperties.MessageState
AQNotificationEvent.AdditionalEventType
AQNotificationEvent.EventType

Package oracle.jdbc.aq Description

This package is an Oracle JDBC extension that provides interfaces to access the Advanced Queuing feature of Oracle for enterprise messaging applications. JDBC AQ supports only the operational interfaces and not the administrative interface, but administrative operations can be accessed through embedded PL/SQL calls.

Enqueuing refers to sending a message to a queue and dequeuing refers to receiving one. A client application can create a message, set the desired properties on it and enqueue it by storing the message in the queue, a table in the database. When dequeuing a message, an application can either dequeue it synchronously by calling the dequeue method on the connection, or asynchronously by waiting for a notification from the database (see the registerAQNotification method on the database).

Skip navigation links