QPID-664: Updates to address options to stay in-line with python client changes in r926604

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@927144 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 4 insertions, 6 deletions

diff --git a/qpid/cpp/examples/messaging/readme.txt b/qpid/cpp/examples/messaging/readme.txt
index 0430b8e2da..ff145e0160 100644
--- a/qpid/cpp/examples/messaging/readme.txt
+++ b/qpid/cpp/examples/messaging/readme.txt
@@ -96,7 +96,7 @@ of address (as there is no existing entity from which to infer that
 type and as we do not want the default type to be created, namely a
 queue):
 
-* run: ./drain -f --address 'my-new-topic; {create: always, node-properties:{type:topic}}'
+* run: ./drain -f --address 'my-new-topic; {create: always, node:{type:topic}}'
 * then run: ./spout --address my-new-queue
 
 The value to the create policy is one of always, sender, receiver or
@@ -128,19 +128,17 @@ qpid-config or even auto-create one):
 An example using xquery based filtering with the xml exchange:
 
 * First start a subscriber with an xquery filter specified:
-  ./drain -f --address 'xml/my-subject; {filter:{xquery:"declare variable $colour external; $colour = '\''red'\''"}}'
+  ./drain -f --address 'xml; {link:{x-bindings:[{arguments:{xquery:"declare variable $colour external; $colour = '\''red'\''"}}]}}'
 
 * Then test receipt of messages that match the xquery filter:
-  ./spout --address 'xml/my-subject' --property colour=red --content 'matched!'
+  ./spout --address 'xml' --property colour=red --content 'matched!'
     and
-  ./spout --address 'xml/my-subject' --property colour=blue --content 'not matched'
+  ./spout --address 'xml' --property colour=blue --content 'not matched'
 
 TODO:
 
 * auto-creating exchanges of different types
 
-* xml content in the xquery example
-
 * 'durable' and 'reliable' subscriptions
 
 * map content