Advanced Queuing - Oracle

JMS Point-to-Point Model Features
The selector for queues containing payloads of type TextMessage,
StreamMessage, BytesMessage, ObjectMessage, MapMessage can contain
any expression that has a combination of one or more of the following:
JMSMessageID =’ID:23452345’ to retrieve messages that have a specified
message ID (all message IDs being prefixed with ID:)
JMS Message header fields or properties:
JMSPriority < 3 AND JMSCorrelationID = ’Fiction’
JMSCorrelationID LIKE ’RE%’
User-defined message properties:
color IN (’RED’, BLUE’, ’GREEN’) AND price < 30000
For queues containing AdtMessages the selector must be a SQL expression on the
message payload contents or message ID or priority or correlation ID.
Selector on message id - to retrieve messages that have a specific message ID
msgid = ’23434556566767676’
Note: in this case message IDs must NOT be prefixed with ’ID:’
Selector on priority or correlation is specified as follows
priority < 3 AND corrid = ’Fiction’
Selector on message payload is specified as follows
tab.user_data.color = ’GREEN’ AND tab.user_data.price < 30000
Example Scenario and Code
In the BOL application, new orders are retrieved from the new_orders_queue.
These orders are then published to the OE.OE_bookedorders_topic. After
creating a JMS connection and session, you create a receiver to receive messages:
public void get_new_orders(QueueSession jms_session)
{
QueueReceiver receiver;
Queue queue;
ObjectMessage obj_message;
BolOrder new_order;
BolCustomer customer;
String state;
String cust_name;
12-40 Oracle9i Application Developer’s Guide - Advanced Queuing