Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04.html (original) +++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04.html Wed Feb 2 22:58:35 2011 @@ -1,4 +1,4 @@ -Chapter 4. Management Tools

Chapter 4. Management Tools

Table of Contents

4.1. +Chapter 4. Management Tools

4.1.  MessageStore Tool

4.1.1.  MessageStore Tool Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04s02.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04s02.html (original) +++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/ch04s02.html Wed Feb 2 22:58:35 2011 @@ -1,6 +1,6 @@ 4.2.  Qpid Java Broker Management CLI

4.2.  + Prev Chapter 4. Management Tools 

4.2.  Qpid Java Broker Management CLI

4.2.1.  How to Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html (original) +++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html Wed Feb 2 22:58:35 2011 @@ -1,4 +1,4 @@ -

List of Tables

1.1. +

List of Tables

1.1. Command Line Options -
2.1. File Format and Principal Database
2.2.
2.3.
2.4.
2.5.
+
2.1. File Format and Principal Database
2.2.
2.3.
2.4.
2.5.

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/pt01.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/pt01.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/pt01.html (original) +++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/pt01.html Wed Feb 2 22:58:35 2011 @@ -1,4 +1,4 @@ -Part I. AMQP Messaging Broker (Implemented in Java)

Part I. AMQP Messaging Broker (Implemented in Java)

Qpid provides two AMQP messaging brokers:

  • Implemented in C++ - high performance, low latency, and RDMA support.

  • Implemented in Java - Fully JMS compliant, runs on any Java platform.

Both AMQP messaging brokers support clients in multiple languages, as long as the messaging client and the messaging broker use the same version of AMQP. See ??? to see which messaging clients work with each broker.

This section contains information specific to the broker that is implemented in Java.

Table of Contents

1. General User Guides
1.1. +Part I. AMQP Messaging Broker (Implemented in Java)

Part I. AMQP Messaging Broker (Implemented in Java)

Qpid provides two AMQP messaging brokers:

  • Implemented in C++ - high performance, low latency, and RDMA support.

  • Implemented in Java - Fully JMS compliant, runs on any Java platform.

Both AMQP messaging brokers support clients in multiple languages, as long as the messaging client and the messaging broker use the same version of AMQP. See ??? to see which messaging clients work with each broker.

This section contains information specific to the broker that is implemented in Java.

2. How Tos
2.1. Add New Users
2.1.1. Available @@ -100,11 +100,11 @@ Priority Queues
2.10.3. Client configuration/messaging model for priority queues -
2.11. Slow Consumer Disconnect - User Guide
2.11.1. Introduction
2.11.2. What can it do?
2.11.3. Frequency of SCD Checking
2.11.4. Client Exceptions
2.11.5. Disconnection Thresholds
2.11.6. Important Points To Note
3. +
2.11. Slow Consumer Disconnect - User Guide
2.11.1. Introduction
2.11.2. What can it do?
2.11.3. Frequency of SCD Checking
2.11.4. Client Exceptions
2.11.5. Disconnection Thresholds
2.11.6. Important Points To Note
3. Qpid JMX Management Console
3.1. Qpid JMX Management Console
3.1.1. Overview -
4. Management Tools
4.1. +
4. Management Tools
4.1. MessageStore Tool
4.1.1. MessageStore Tool Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/pdf/AMQP-Messaging-Broker-Java-Book.pdf URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/pdf/AMQP-Messaging-Broker-Java-Book.pdf?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== Binary files - no diff available. Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch01.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch01.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch01.html (original) +++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch01.html Wed Feb 2 22:58:35 2011 @@ -1,16 +1,16 @@ -Chapter 1. Introduction

Chapter 1. Introduction

Apache Qpid is a reliable, asynchronous messaging system that +Chapter 1. Introduction

Chapter 1. Introduction

Apache Qpid is a reliable, asynchronous messaging system that supports the AMQP messaging protocol in several common programming languages. Qpid is supported on most common platforms.

  • On the Java platform, Qpid uses the established Java JMS - API. + API.

  • For Python, C++, and .NET, Qpid defines its own messaging API, the Qpid Messaging API, which is conceptually similar in each.

    - On the .NET platform, Qpid also provides a WCF binding. + On the .NET platform, Qpid also provides a WCF binding.

  • Ruby will also use the Qpid Messaging API, which will soon be implemented. (Ruby currently uses an API that is closely Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02.html (original) +++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02.html Wed Feb 2 22:58:35 2011 @@ -1,4 +1,4 @@ -Chapter 2. Using the Qpid Messaging API

    Chapter 2. Using the Qpid Messaging API

    The Qpid Messaging API is quite simple, consisting of only a +Chapter 2. Using the Qpid Messaging API

    Chapter 2. Using the Qpid Messaging API

    The Qpid Messaging API is quite simple, consisting of only a handful of core classes.

    • A message consists of a standard set @@ -26,9 +26,9 @@

    The following sections show how to use these classes in a simple messaging program. -

    2.1. A Simple Messaging Program in C++

    The following C++ program shows how to create a connection, +

    2.1. A Simple Messaging Program in C++

    The following C++ program shows how to create a connection, create a session, send messages using a sender, and receive - messages using a receiver.

    Example 2.1. "Hello world!" in C++

    +        messages using a receiver.

    Example 2.1. "Hello world!" in C++

     #include <qpid/messaging/Connection.h>
     #include <qpid/messaging/Message.h>
     #include <qpid/messaging/Receiver.h>
    @@ -43,7 +43,7 @@ int main(int argc, char** argv) {
         std::string broker = argc > 1 ? argv[1] : "localhost:5672";
         std::string address = argc > 2 ? argv[2] : "amq.topic";
         std::string connectionOptions = argc > 3 ? argv[3] : "";
    -    
    +
         Connection connection(broker, connectionOptions);
         try {
             connection.open();  (1)
    @@ -57,13 +57,13 @@ int main(int argc, char** argv) {
             Message message = receiver.fetch(Duration::SECOND * 1); (5)
             std::cout << message.getContent() << std::endl;
             session.acknowledge(); (6)
    -        
    +
             connection.close(); (7)
             return 0;
         } catch(const std::exception& error) {
             std::cerr << error.what() << std::endl;
             connection.close();
    -        return 1;   
    +        return 1;
         }
     }

    (1)

    Establishes the connection with the messaging broker.

    (2)

    Creates a session object on which messages will be sent and received.

    (3)

    Creates a receiver that receives messages from the given address.

    (4)

    Creates a sender that sends to the given address.

    (5)

    Receives the next message. The duration is optional, if omitted, will wait indefinitely for the next message.

    (6)

    Acknowledges receipt of all fetched messages on the session. This informs the broker that the messages were Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s02.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s02.html (original) +++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s02.html Wed Feb 2 22:58:35 2011 @@ -1,6 +1,6 @@ -2.2. A Simple Messaging Program in Python

    2.2. A Simple Messaging Program in Python

    The following Python program shows how to create a +2.2. A Simple Messaging Program in Python

    2.2. A Simple Messaging Program in Python

    The following Python program shows how to create a connection, create a session, send messages using a sender, and - receive messages using a receiver.

    Example 2.2. "Hello world!" in Python

    +        receive messages using a receiver.

    Example 2.2. "Hello world!" in Python

     import sys
     from qpid.messaging import *
     
    
    Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s03.html
    URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s03.html?rev=1066676&r1=1066675&r2=1066676&view=diff
    ==============================================================================
    --- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s03.html (original)
    +++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s03.html Wed Feb  2 22:58:35 2011
    @@ -1,9 +1,9 @@
    -2.3. A Simple Messaging Program in .NET C#

    2.3. A Simple Messaging Program in .NET C#

    The following .NET C# program shows how to create a connection, +2.3. A Simple Messaging Program in .NET C#

    2.3. A Simple Messaging Program in .NET C#

    The following .NET C# + [1] + program shows how to create a connection, create a session, send messages using a sender, and receive - messages using a receiver. The .NET binding for the Qpid C++ Messaging API - applies to all .NET Framework managed code languages. C# was chosen - for illustration purposes only. -

    Example 2.3. "Hello world!" in .NET C#

    +        messages using a receiver.
    +      

    Example 2.3. "Hello world!" in .NET C#

     using System;
     using Org.Apache.Qpid.Messaging;  (1)
     
    @@ -39,6 +39,10 @@ namespace Org.Apache.Qpid.Messaging {
         }
     }
     
    -

    (1)

    Selects the Qpid Messaging namespace. A project reference to the Org.Apache.Qpid.Messaging dll defines the Qpid Messaging namespace objects and methods.

    (2)

    Establishes the connection with the messaging broker.

    (3)

    Creates a session object on which messages will be sent and received.

    (4)

    Creates a receiver that receives messages from the given address.

    (5)

    Creates a sender that sends to the given address.

    (6)

    Receives the next message. The duration is optional, if omitted, will wait indefinitely for the next message.

    (7)

    Acknowledges receipt of all fetched messages on the +

    (1)

    Permits use of Org.Apache.Qpid.Messaging types and methods without explicit namespace qualification. Any .NET project must have a project reference to the assembly file Org.Apache.Qpid.Messaging.dll in order to obtain the definitions of the .NET Binding for Qpid Messaging namespace.

    (2)

    Establishes the connection with the messaging broker.

    (3)

    Creates a session object on whic h messages will be sent and received.

    (4)

    Creates a receiver that receives messages from the given address.

    (5)

    Creates a sender that sends to the given address.

    (6)

    Receives the next message. The duration is optional, if omitted, will wait indefinitely for the next message.

    (7)

    A cknowledges receipt of all fetched messages on the session. This informs the broker that the messages were - transfered and processed by the client successfully.

    (8)

    Closes the connection, all sessions managed by the connection, and all senders and receivers managed by each session.





    [1] + The .NET binding for the Qpid C++ Messaging API + applies to all .NET Framework managed code languages. C# was chosen + for illustration purposes only. +

    Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s04.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s04.html?rev=1066676&r1=1066675&r2=1066676&view=diff ============================================================================== --- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s04.html (original) +++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch02s04.html Wed Feb 2 22:58:35 2011 @@ -1,8 +1,8 @@ 2.4. Addresses

    2.4. Addresses

    An address is the name of a message - target or message source. + target or message source. + + [2] - [1] - The methods that create senders and receivers require an address. The details of sending to a particular target or receiving from a particular source are then handled by the @@ -12,22 +12,22 @@ Qpid Messaging API recognises two kinds of nodes, queues and topics - [2]. + [3]. A queue stores each message until it has been received and acknowledged, and only one receiver can receive a given message - [3]. + [4]. A topic immediately delivers a message to all eligible receivers; if there are no eligible receivers, it discards the message. In the AMQP 0-10 implementation of the API, - - [4] + + [5] queues map to AMQP queues, and topics map to AMQP exchanges. - [5] + [6]

    In the rest of this tutorial, we present many examples using two programs that take an address as a command line parameter. spout sends messages to the @@ -37,15 +37,15 @@ language. These programs can use any address string as a source or a destination, and have many command line options to configure behavior—use the -h option - for documentation on these options. + for documentation on these options. - [6] + [7] The examples in this tutorial also use the qpid-config utility to configure AMQP 0-10 queues and exchanges on a Qpid broker. -

    Example 2.4. Queues

    Create a queue with qpid-config, send a message using +

    Example 2.4. Queues

    Create a queue with qpid-config, send a message using spout, and read it using drain:

     $ qpid-config add queue hello-world
     $ ./spout hello-world
    @@ -58,7 +58,7 @@ Message(properties={spout-id:c877e622-d5
     	drain one more time, no messages will be retrieved.

     $ ./drain hello-world
     $
    -	

    Example 2.5. Topics

    This example is similar to the previous example, but it +


    Example 2.5. Topics

    This example is similar to the previous example, but it uses a topic instead of a queue.

    First, use qpid-config to remove the queue and create an exchange with the same name:

     $ qpid-config del queue hello-world
    @@ -85,7 +85,7 @@ $ ./spout hello-word
     Message(properties={spout-id:7da2d27d-93e6-4803-8a61-536d87b8d93f:0}, content='')
             

    You can run drain in several separate windows; each creates a subscription for the exchange, and - each receives all messages sent to the exchange.


    2.4.1. Address Strings

    So far, our examples have used address strings that + each receives all messages sent to the exchange.


    2.4.1. Address Strings

    So far, our examples have used address strings that contain only the name of a node. An address string can also contain a subject and @@ -97,13 +97,13 @@ options ::= { <key> : <value&g maps, or lists. A complete BNF for address strings appears in Section 2.4.4, “Address String Grammar”.

    So far, the address strings in this tutorial have only used simple names. The following sections show how to use - subjects and options.

    2.4.2. Subjects

    Every message has a property called + subjects and options.

    2.4.2. Subjects

    Every message has a property called subject, which is analogous to the subject on an email message. If no subject is specified, the message's subject is null. For convenience, address strings also allow a subject. If a sender's address contains a subject, it is used as the default subject for the messages - it sends. + it sends. If a receiver's address contains a subject, it is used to select only messages that match the subject—the matching @@ -116,7 +116,7 @@ options ::= { <key> : <value&g Currently, a receiver bound to a queue ignores subjects, receiving messages from the queue without filtering. Support for subject filtering on queues will be implemented soon. -

    Example 2.6. Using subjects

    In this example we show how subjects affect message +

    Example 2.6. Using subjects

    In this example we show how subjects affect message flow.

    First, let's use qpid-config to create a topic exchange.

     $ qpid-config add exchange topic news-service
             

    Now we use drain to receive messages from news-service that match the subject sports.

    First Window:

    @@ -140,11 +140,11 @@ Message(properties={qpid.subject:sports,
     	application, the sender might use subjects like
     	usa.news, usa.weather,
     	europe.news, or
    -	europe.weather. 
    +	europe.weather.
     
     	The receiver's subject can include wildcard characters—
     	# matches one or more words in the message's
    -	subject, * matches a single word. 
    +	subject, * matches a single word.
     
     	For instance, if the subject in the source address is
     	*.news, it matches messages with the
    @@ -152,7 +152,7 @@ Message(properties={qpid.subject:sports,
     	usa.news; if it is
     	europe.#, it matches messages with subjects
     	like europe.news or
    -	europe.pseudo.news.

    Example 2.7. Subjects with multi-word keys

    This example uses drain and spout to demonstrate the + europe.pseudo.news.

    Example 2.7. Subjects with multi-word keys

    This example uses drain and spout to demonstrate the use of subjects with two-word keys.

    Let's use drain with the subject *.news to listen for messages in which the second word of the key is @@ -187,7 +187,7 @@ $ ./spout news-service/usa.faux.sports Message(properties={qpid.subject:news, spout-id:cbd42b0f-c87b-4088-8206-26d7627c9640:0}, content='') Message(properties={qpid.subject:usa.news, spout-id:234a78d7-daeb-4826-90e1-1c6540781eac:0}, content='') Message(properties={qpid.subject:usa.faux.news, spout-id:6029430a-cfcb-4700-8e9b-cbe4a81fca5f:0}, content='') -


    2.4.3. Address String Options

    +


    2.4.3. Address String Options

    The options in an address string can contain additional information for the senders or receivers created for it, including: @@ -203,7 +203,7 @@ Message(properties={qpid.subject:usa.fau

  • Policies for automatically creating or deleting the node to which an address refers.

    - For instance, in the address string xoxox ; {create: always}, + For instance, in the address string xoxox ; {create: always}, the queue xoxox is created, if it does not exist, before the address is resolved.

  • @@ -223,11 +223,11 @@ Message(properties={qpid.subject:usa.fau Let's use some examples to show how these different kinds of address string options affect the behavior of senders and receives. -

    2.4.3.1. assert

    +

    2.4.3.1. assert

    In this section, we use the assert option to ensure that the address resolves to a node of the required type. -

    Example 2.8. Assertions on Nodes

    Let's use qpid-config to create a +

    Example 2.8. Assertions on Nodes

    Let's use qpid-config to create a queue and a topic.

     $ qpid-config add queue my-queue
     $ qpid-config add exchange topic my-topic
    @@ -252,15 +252,15 @@ $ ./drain 'my-topic; {assert: always, no
     Queue my-topic does not exist
     	

    Now let's use the create option to create the queue xoxox if it does not already - exist:

    2.4.3.2. create

    In previous examples, we created the queue before + exist:

    2.4.3.2. create

    In previous examples, we created the queue before listening for messages on it. Using create: always, the queue is automatically created if it - does not exist.

    Example 2.9. Creating a Queue Automatically

    First Window:

    $ ./drain -t 30 "xoxox ; {create: always}"

    Now we can send messages to this queue:

    Second Window:

    $ ./spout "xoxox ; {create: always}"

    Returning to the first window, we see that drain has received this message:

    Message(properties={spout-id:1a1a3842-1a8b-4f88-8940-b4096e615a7d:0}, content='')

    The details of the node thus created can be controlled by further options within the node. See Table 2.2, “Node Properties” for details.

    2.4.3.3. browse

    Some options specify message transfer semantics; for + does not exist.

    Example 2.9. Creating a Queue Automatically

    First Window:

    $ ./drain -t 30 "xoxox ; {create: always}"

    Now we can send messages to this queue:

    Second Window:

    $ ./spout "xoxox ; {create: always}"

    Returning to the first window, we see that drain has received this message:

    Message(properties={spout-id:1a1a3842-1a8b-4f88-8940-b4096e615a7d:0}, content='')

    The details of the node thus created can be controlled by further options within the node. See Table 2.2, “Node Properties” for details.

    2.4.3.3. browse

    Some options specify message transfer semantics; for instance, they may state whether messages should be consumed or read in browsing mode, or specify reliability characteristics. The following example uses the browse option to receive messages without - removing them from a queue.

    Example 2.10. Browsing a Queue

    + removing them from a queue.

    Example 2.10. Browsing a Queue

    Let's use the browse mode to receive messages without removing them from the queue. First we send three messages to the queue: @@ -278,7 +278,7 @@ $ ./drain 'my-queue; {mode: browse}' Message(properties={spout-id:fbb93f30-0e82-4b6d-8c1d-be60eb132530:0}, content='one') Message(properties={spout-id:ab9e7c31-19b0-4455-8976-34abe83edc5f:0}, content='two') Message(properties={spout-id:ea75d64d-ea37-47f9-96a9-d38e01c97925:0}, content='three') -


    2.4.3.4. x-bindings

    Greater control over the AMQP 0-10 binding process can +


    2.4.3.4. x-bindings

    Greater control over the AMQP 0-10 binding process can be achieved by including an x-bindings option in an address string. @@ -301,23 +301,23 @@ $ qpid-config add exchange xml xml element is named weather. Here is an address string that contains this query:

     xml; {
    - link: { 
    -  x-bindings: [{exchange:xml, key:weather, arguments:{xquery:"./weather"} }] 
    - } 
    + link: {
    +  x-bindings: [{exchange:xml, key:weather, arguments:{xquery:"./weather"} }]
    + }
     }
       

    When using longer queries with drain, it is often useful to place the query in a file, and use cat in the command line. We do this in the - following example.

    Example 2.11. Using the XML Exchange

    This example uses an x-binding that contains queries, which filter based on the content of XML messages. Here is an XQuery that we will use in this example:

    +	following example.

    Example 2.11. Using the XML Exchange

    This example uses an x-binding that contains queries, which filter based on the content of XML messages. Here is an XQuery that we will use in this example:

     	  
    -let $w := ./weather 
    -return $w/station = 'Raleigh-Durham International Airport (KRDU)' 
    +let $w := ./weather
    +return $w/station = 'Raleigh-Durham International Airport (KRDU)'
        and $w/temperature_f > 50
        and $w/temperature_f - $w/dewpoint > 5
        and $w/wind_speed_mph > 7
        and $w/wind_speed_mph < 20 
     	

    We can specify this query in an x-binding to listen to messages that meet the criteria specified by the query:

    First Window:

    -$ ./drain -f "xml; {link:{x-bindings:[{key:'weather', 
    +$ ./drain -f "xml; {link:{x-bindings:[{key:'weather',
     arguments:{xquery:\"$(cat rdu.xquery )\"}}]}}"
     	

    In another window, let's create an XML message that meets the criteria in the query, and place it in the file rdu.xml:

     
    @@ -330,14 +330,14 @@ arguments:{xquery:\"$(cat rdu.xquery )\"
     	

    Now let's use spout to send this message to the XML exchange:

    Second Window:

     spout --content "$(cat rdu.xml)" xml/weather
     	

    Returning to the first window, we see that the message has been received:

    $ ./drain -f "xml; {link:{x-bindings:[{exchange:'xml', key:'weather', arguments:{xquery:\"$(cat rdu.xquery )\"}}]}}"
    -Message(properties={qpid.subject:weather, spout-id:31c431de-593f-4bec-a3dd-29717bd945d3:0}, 
    +Message(properties={qpid.subject:weather, spout-id:31c431de-593f-4bec-a3dd-29717bd945d3:0},
     content='<weather>
       <station>Raleigh-Durham International Airport (KRDU)</station>
       <wind_speed_mph>16</wind_speed_mph>
       <temperature_f>40</temperature_f>
       <dewpoint>35</dewpoint>
     </weather>') 
    -	

    2.4.3.5. Address String Options - Reference

    Table 2.1. Address String Options

    optionvaluesemantics
    +

    2.4.3.5. Address String Options - Reference

    Table 2.1. Address String Options

    optionvaluesemantics
    assert one of: always, never, sender or receiver @@ -424,9 +424,9 @@ content='<weather> exchange: <exchange>, queue: <queue>, key: <key>, - arguments: { - <key_1>: <value_1>, - ..., + arguments: { + <key_1>: <value_1>, + ..., <key_n>: <value_n> } }, ... @@ -454,7 +454,7 @@ content='<weather> that a message is not lost, and is delivered precisely once. Currently only unreliable and at-least-once are supported. - [a] + [a]
    durable @@ -489,7 +489,7 @@ content='<weather> independent of the create option. They are considered logically part of the linking process rather than of node creation. -

    [a] If at-most-once is requested, +

    [a] If at-most-once is requested, unreliable will be used and for durable messages on durable queues there is the possibility that messages will be redelivered; if exactly-once is requested, @@ -545,10 +545,10 @@ options := map

    Create, Delete, and Assert Policies

    The create, delete, and assert policies specify who should perfom the associated action:

    • always: the action is performed by any messaging client

    • sender: the action is only performed by a sender

    • receiver: the action is only performed by a receiver

    • never: the action is never performed (this is the default)

    Node-Type

    The node-type is one of:

    • topic: in the AMQP 0-10 mapping, a topic node defaults to the topic exchange, x-declare - may be used to specify other exchange types

    • queue: this is the default node-type



    [1] In the programs we have just seen, we used + may be used to specify other exchange types

  • queue: this is the default node-type



  • [2] In the programs we have just seen, we used amq.topic as the default address if none is passed in. This is the name of a standard exchange that always - exists on an AMQP 0-10 messaging broker.

    [2] The terms queue and + exists on an AMQP 0-10 messaging broker.

    [3] The terms queue and topic here were chosen to align with their meaning in JMS. These two addressing 'patterns', queue and topic, are sometimes refered as point-to-point @@ -556,11 +556,11 @@ options := map called a topic exchange. When the term topic occurs alone, it refers to a Messaging API topic, not the topic - exchange.

    [3] There are exceptions to this rule; for instance, + exchange.

    [4] There are exceptions to this rule; for instance, a receiver can use browse mode, which leaves messages on the queue for other receivers to - read.

    [4] The AMQP 0-10 implementation is the only one - that currently exists.

    [5] In AMQP 0-10, messages are sent to + read.

    [5] The AMQP 0-10 implementation is the only one + that currently exists.

    [6] In AMQP 0-10, messages are sent to exchanges, and read from queues. The Messaging API also allows a sender to send messages to a queue; internally, Qpid implements this by sending the message to the default @@ -569,7 +569,7 @@ options := map from a topic; internally, Qpid implements this by setting up a private subscription queue for the receiver and binding the subscription queue to the exchange that corresponds to - the topic.

    [6] Currently, the C++, Python, and .NET C# + the topic.

    [7] Currently, the C++, Python, and .NET C# implementations of drain and spout have slightly different options. This tutorial uses the C++ implementation. The --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:commits-subscribe@qpid.apache.org