You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ac...@apache.org on 2012/04/05 21:34:26 UTC
svn commit: r1310030 [13/14] - in /qpid/site/docs/books/trunk:
AMQP-Messaging-Broker-CPP-Book/html-single/
AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/pdf/
AMQP-Messaging-Broker-Java-Book/html-single/ AMQP-Messaging-Broker-Java-...
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/index.html?rev=1310030&r1=1310029&r2=1310030&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/index.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/index.html Thu Apr 5 19:34:23 2012
@@ -1 +1 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Programming in Apache Qpid</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="next" href="ch01.html" title="Chapter 1. Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Programming in Apache Qpid</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch01.html">Next</a></td></tr></table><hr></div><div class="book" title="Programming in Apache Qpid"><div class="titlepage"><div><div><h1 class="title"><a name="client-api-tutorial"></a>Programming in Apache Qpid</h1></div><div><h2 c
lass="subtitle">Cross-Platform AMQP Messaging in Java JMS, .NET, C++, and Python</h2></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch01.html">1. Introduction</a></span></dt><dt><span class="chapter"><a href="ch02.html">2. Using the Qpid Messaging API</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#id336276">2.1. A Simple Messaging Program in C++</a></span></dt><dt><span class="section"><a href="ch02s02.html">2.2. A Simple Messaging Program in Python</a></span></dt><dt><span class="section"><a href="ch02s03.html">2.3. A Simple Messaging Program in .NET C#</a></span></dt><dt><span class="section"><a href="section-addresses.html">2.4. Addresses</a></span></dt><dd><dl><dt><span class="section"><a href="section-addresses.html#id381641">2.4.1. Address Strings</a></span></dt><dt><span class="section"><a href="section-addresses.html#id381684">2.4.2. Subjects</a></span></dt><dt><span class="section"><a
href="section-addresses.html#id382022">2.4.3. Address String Options</a></span></dt><dt><span class="section"><a href="section-addresses.html#section-address-string-bnf">2.4.4. Address String Grammar</a></span></dt></dl></dd><dt><span class="section"><a href="replay.html">2.5. Sender Capacity and Replay</a></span></dt><dt><span class="section"><a href="prefetch.html">2.6. Receiver Capacity (Prefetch)</a></span></dt><dt><span class="section"><a href="acknowledgements.html">2.7. Acknowledging Received Messages</a></span></dt><dt><span class="section"><a href="ch02s08.html">2.8. Receiving Messages from Multiple Sources</a></span></dt><dt><span class="section"><a href="ch02s09.html">2.9. Transactions</a></span></dt><dt><span class="section"><a href="connection-options.html">2.10. Connection Options</a></span></dt><dt><span class="section"><a href="section-Maps.html">2.11. Maps and Lists in Message Content</a></span></dt><dd><dl><dt><span class="section"><a href="section-Maps.ht
ml#section-Python-Maps">2.11.1. Qpid Maps and Lists in Python</a></span></dt><dt><span class="section"><a href="section-Maps.html#section-cpp-Maps">2.11.2. Qpid Maps and Lists in C++</a></span></dt><dt><span class="section"><a href="section-Maps.html#section-dotnet-Maps">2.11.3. Qpid Maps and Lists in .NET</a></span></dt></dl></dd><dt><span class="section"><a href="ch02s12.html">2.12. The Request / Response Pattern</a></span></dt><dt><span class="section"><a href="ch02s13.html">2.13. Performance Tips</a></span></dt><dt><span class="section"><a href="ch02s14.html">2.14. Cluster Failover</a></span></dt><dt><span class="section"><a href="ch02s15.html">2.15. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="ch02s15.html#id384722">2.15.1. Logging in C++</a></span></dt><dt><span class="section"><a href="ch02s15.html#id384763">2.15.2. Logging in Python</a></span></dt></dl></dd><dt><span class="section"><a href="section-amqp0-10-mapping.html">2.16. The AMQP 0-10 mapp
ing</a></span></dt><dd><dl><dt><span class="section"><a href="section-amqp0-10-mapping.html#section-amqp0-10-message-props">2.16.1. 0-10 Message Property Keys</a></span></dt></dl></dd><dt><span class="section"><a href="Message-Groups-Guide.html">2.17. Using Message Groups</a></span></dt><dd><dl><dt><span class="section"><a href="Message-Groups-Guide.html#messagegroups-setup">2.17.1. Creating Message Group Queues</a></span></dt><dt><span class="section"><a href="Message-Groups-Guide.html#messagegroups-sending">2.17.2. Sending Grouped Messages</a></span></dt><dt><span class="section"><a href="Message-Groups-Guide.html#messagegroups-receiving">2.17.3. Receiving Grouped Messages</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="QpidJMS.html">3. Using the Qpid JMS client</a></span></dt><dd><dl><dt><span class="section"><a href="QpidJMS.html#id385348">3.1. A Simple Messaging Program in Java JMS</a></span></dt><dt><span class="section"><a href="QpidJNDI.html">3.
2. Apache Qpid JNDI Properties for AMQP Messaging</a></span></dt><dd><dl><dt><span class="section"><a href="QpidJNDI.html#id385703">3.2.1. JNDI Properties for Apache Qpid</a></span></dt><dt><span class="section"><a href="QpidJNDI.html#section-jms-connection-url">3.2.2. Connection URLs</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s03.html">3.3. Java JMS Message Properties</a></span></dt><dt><span class="section"><a href="section-JMS-MapMessage.html">3.4. JMS MapMessage Types</a></span></dt><dt><span class="section"><a href="section-JMS-Logging.html">3.5. JMS Client Logging</a></span></dt><dt><span class="section"><a href="ch03s06.html">3.6. Configuring the JMS Client</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s06.html#client-jvm-properties">3.6.1. Qpid JVM Arguments</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="QpidWCF.html">4. Using the Qpid WCF client</a></span></dt><dd><dl><dt><span class="section"><a href="Qpid
WCF.html#id388018">4.1. XML and Binary Bindings</a></span></dt><dt><span class="section"><a href="ch04s02.html">4.2. Endpoints</a></span></dt><dt><span class="section"><a href="ch04s03.html">4.3. Message Headers</a></span></dt><dt><span class="section"><a href="ch04s04.html">4.4. Security</a></span></dt><dt><span class="section"><a href="ch04s05.html">4.5. Transactions</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch05.html">5. The .NET Binding for the C++ Messaging Client</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#id388409">5.1. .NET Binding for the C++ Messaging Client Component Architecture</a></span></dt><dt><span class="section"><a href="ch05s02.html">5.2. .NET Binding for the C++ Messaging Client Examples</a></span></dt><dt><span class="section"><a href="ch05s03.html">5.3. .NET Binding Class Mapping to Underlying C++ Messaging API</a></span></dt><dd><dl><dt><span class="section"><a href="ch05s03.html#id388943">5.3.1. .NET Binding
for the C++ Messaging API Class: Address</a></span></dt><dt><span class="section"><a href="ch05s03.html#id389533">5.3.2. .NET Binding for the C++ Messaging API Class: Connection</a></span></dt><dt><span class="section"><a href="ch05s03.html#id390159">5.3.3. .NET Binding for the C++ Messaging API Class: Duration</a></span></dt><dt><span class="section"><a href="ch05s03.html#id390570">5.3.4. .NET Binding for the C++ Messaging API Class: FailoverUpdates</a></span></dt><dt><span class="section"><a href="ch05s03.html#id390746">5.3.5. .NET Binding for the C++ Messaging API Class: Message</a></span></dt><dt><span class="section"><a href="ch05s03.html#id391898">5.3.6. .NET Binding for the C++ Messaging API Class: Receiver</a></span></dt><dt><span class="section"><a href="ch05s03.html#id392527">5.3.7. .NET Binding for the C++ Messaging API Class: Sender</a></span></dt><dt><span class="section"><a href="ch05s03.html#id392998">5.3.8. .NET Binding for the C++ Messaging API Class: Sessio
n</a></span></dt><dt><span class="section"><a href="ch05s03.html#id393934">5.3.9. .NET Binding Class: SessionReceiver</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="section-addresses.html#id382503">Address String Options</a></dt><dt>2.2. <a href="section-addresses.html#table-node-properties">Node Properties</a></dt><dt>2.3. <a href="section-addresses.html#table-link-properties">Link Properties</a></dt><dt>2.4. <a href="connection-options.html#id383470">Connection Options</a></dt><dt>2.5. <a href="section-Maps.html#tabl-Programming_in_Apache_Qpid-Qpid_Maps_in_Message_Content">Map and List Representation in Supported Languages</a></dt><dt>2.6. <a href="section-Maps.html#table-Python-Maps">Python Datatypes in Maps</a></dt><dt>2.7. <a href="section-Maps.html#table-cpp-Maps">C++ Datatypes in Maps</a></dt><dt>2.8. <a href="section-Maps.html#table-dotnet-Maps">Datatype Mapping between C++ and .NET binding<
/a></dt><dt>2.9. <a href="section-amqp0-10-mapping.html#table-amqp0-10-message-properties">Mapping to AMQP 0-10 Message Properties</a></dt><dt>3.1. <a href="QpidJNDI.html#id385712">JNDI Properties supported by Apache Qpid</a></dt><dt>3.2. <a href="QpidJNDI.html#id385840">Connection URL Properties</a></dt><dt>3.3. <a href="QpidJNDI.html#id386108">Broker List Options</a></dt><dt>3.4. <a href="ch03s03.html#id386430">Java JMS Mapping to AMQP 0-10 Message Properties</a></dt><dt>3.5. <a href="section-JMS-MapMessage.html#table-Java-Maps">Java Datatypes in Maps</a></dt><dt>3.6. <a href="ch03s06.html#id386903">Config Options For Connection Behaviour</a></dt><dt>3.7. <a href="ch03s06.html#id387003">Config Options For Session Behaviour</a></dt><dt>3.8. <a href="ch03s06.html#id387114">Config Options For Consumer Behaviour</a></dt><dt>3.9. <a href="ch03s06.html#id387243">Config Options For Producer Behaviour</a></dt><dt>3.10. <a href="ch03s06.html#id387302">Config Options For Threading</
a></dt><dt>3.11. <a href="ch03s06.html#id387377">Config Options For I/O</a></dt><dt>3.12. <a href="ch03s06.html#id387546">Config Options For Security</a></dt><dt>3.13. <a href="ch03s06.html#id387671">Config Options For Security - Standard JVM properties needed when using GSSAPI as the SASL mechanism.</a></dt><dt>3.14. <a href="ch03s06.html#id387757">Config Options For Security - Using SSL for securing connections or using EXTERNAL as the SASL mechanism.</a></dt><dt>3.15. <a href="ch03s06.html#id387870">Config Options For Security - Standard JVM properties needed when Using SSL for securing connections or using EXTERNAL as the SASL mechanism.</a></dt><dt>4.1. <a href="QpidWCF.html#id388102">WCF Binding Parameters</a></dt><dt>5.1. <a href="ch05.html#table-Dotnet-Binding-Component-Architecture">.NET Binding for the C++ Messaging Client Component Architecture</a></dt><dt>5.2. <a href="ch05s02.html#table-Dotnet-Binding-Example-Client-Server">Example : Client - Server</a></dt><dt>
5.3. <a href="ch05s02.html#table-Dotnet-Binding-Example-MapSender-MapReceiver">Example : Map Sender â Map Receiver</a></dt><dt>5.4. <a href="ch05s02.html#table-Dotnet-Binding-Example-Spout-Drain">Example : Spout - Drain</a></dt><dt>5.5. <a href="ch05s02.html#table-Dotnet-Binding-Example-CallbackSender-CallbackReceiver">Example : Map Callback Sender â Map Callback Receiver</a></dt><dt>5.6. <a href="ch05s02.html#table-Dotnet-Binding-Example-DeclareQueues">Example - Declare Queues</a></dt><dt>5.7. <a href="ch05s02.html#table-Dotnet-Binding-Example-DirectSender-DirectReceiver">Example: Direct Sender - Direct Receiver</a></dt><dt>5.8. <a href="ch05s02.html#table-Dotnet-Binding-Example-Helloworld">Example: Hello World</a></dt><dt>5.9. <a href="ch05s03.html#table-Dotnet-Binding-Address">.NET Binding for the C++ Messaging API Class: Address</a></dt><dt>5.10. <a href="ch05s03.html#table-Dotnet-Binding-Connection">.NET Binding for the C++ Messaging API Class: Connection</a><
/dt><dt>5.11. <a href="ch05s03.html#table-Dotnet-Binding-Duration">.NET Binding for the C++ Messaging API Class: Duration</a></dt><dt>5.12. <a href="ch05s03.html#table-Dotnet-Binding-FailoverUpdates">.NET Binding for the C++ Messaging API Class: FailoverUpdates</a></dt><dt>5.13. <a href="ch05s03.html#table-Dotnet-Binding-Message">.NET Binding for the C++ Messaging API Class: Message</a></dt><dt>5.14. <a href="ch05s03.html#table-Dotnet-Binding-Receiver">.NET Binding for the C++ Messaging API Class: Receiver</a></dt><dt>5.15. <a href="ch05s03.html#table-Dotnet-Binding-Sender">.NET Binding for the C++ Messaging API Class: Sender</a></dt><dt>5.16. <a href="ch05s03.html#table-Dotnet-Binding-Session">.NET Binding for the C++ Messaging API Class: Session</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>2.1. <a href="ch02.html#id336286">"Hello world!" in C++</a></dt><dt>2.2. <a href="ch02s02.html#id335528">"Hello world!" in Python</a></dt><dt>2.
3. <a href="ch02s03.html#id381123">"Hello world!" in .NET C#</a></dt><dt>2.4. <a href="section-addresses.html#id381432">Queues</a></dt><dt>2.5. <a href="section-addresses.html#id381506">Topics</a></dt><dt>2.6. <a href="section-addresses.html#id381717">Using subjects</a></dt><dt>2.7. <a href="section-addresses.html#id381890">Subjects with multi-word keys</a></dt><dt>2.8. <a href="section-addresses.html#id382137">Assertions on Nodes</a></dt><dt>2.9. <a href="section-addresses.html#id382217">Creating a Queue Automatically</a></dt><dt>2.10. <a href="section-addresses.html#id382285">Browsing a Queue</a></dt><dt>2.11. <a href="section-addresses.html#id382398">Using the XML Exchange</a></dt><dt>2.12. <a href="ch02s08.html#id383266">Receiving Messages from Multiple Sources</a></dt><dt>2.13. <a href="ch02s09.html#id383333">Transactions</a></dt><dt>2.14. <a href="connection-options.html#id383377">Specifying Connection Options in C++, Python, and .NET</a></dt><dt>2.15. <a href="section
-Maps.html#id383939">Sending Qpid Maps and Lists in Python</a></dt><dt>2.16. <a href="section-Maps.html#id384097">Sending Qpid Maps and Lists in C++</a></dt><dt>2.17. <a href="section-Maps.html#id384292">Sending Qpid Maps and Lists in .NET C#</a></dt><dt>2.18. <a href="ch02s12.html#id384502">Request / Response Applications in C++</a></dt><dt>2.19. <a href="ch02s14.html#id384666">Tracking cluster membership</a></dt><dt>2.20. <a href="section-amqp0-10-mapping.html#id385290">Accessing the AMQP 0-10 Message Timestamp in Python</a></dt><dt>2.21. <a href="section-amqp0-10-mapping.html#id385310">Accessing the AMQP 0-10 Message Timestamp in C++</a></dt><dt>2.22. <a href="Message-Groups-Guide.html#id382892">Message Group Queue Creation - Python</a></dt><dt>2.23. <a href="Message-Groups-Guide.html#id382906">Message Group Queue Creation - C++</a></dt><dt>2.24. <a href="Message-Groups-Guide.html#id382921">Message Group Queue Creation - Java</a></dt><dt>2.25. <a href="Message-Groups-Guid
e.html#id334753">Sending Grouped Messages - Python</a></dt><dt>2.26. <a href="Message-Groups-Guide.html#id334769">Sending Grouped Messages - C++</a></dt><dt>2.27. <a href="Message-Groups-Guide.html#id334785">Sending Grouped Messages - Java</a></dt><dt>3.1. <a href="QpidJMS.html#id385366">"Hello world!" in Java</a></dt><dt>3.2. <a href="QpidJMS.html#id385607">JNDI Properties File for "Hello world!" example</a></dt><dt>3.3. <a href="QpidJNDI.html#id385684">JNDI Properties File</a></dt><dt>3.4. <a href="QpidJNDI.html#id386064">Broker Lists</a></dt><dt>3.5. <a href="section-JMS-MapMessage.html#id386595">Sending a Java JMS MapMessage</a></dt><dt>3.6. <a href="section-JMS-Logging.html#id386791">log4j Logging Properties</a></dt><dt>4.1. <a href="QpidWCF.html#id388035">Traditional service model "Hello world!" example</a></dt><dt>4.2. <a href="QpidWCF.html#id388063">Binary "Hello world!" example using the channel model</a></dt></dl></div></div><div class="navfooter"><hr><table width
="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Programming in Apache Qpid</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="next" href="ch01.html" title="Chapter 1. Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Programming in Apache Qpid</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch01.html">Next</a></td></tr></table><hr></div><div class="book" title="Programming in Apache Qpid"><div class="titlepage"><div><div><h1 class="title"><a name="client-api-tutorial"></a>Programming in Apache Qpid</h1></div><div><h2 c
lass="subtitle">Cross-Platform AMQP Messaging in Java JMS, .NET, C++, and Python</h2></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch01.html">1. Introduction</a></span></dt><dt><span class="chapter"><a href="ch02.html">2. Using the Qpid Messaging API</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#id533737">2.1. A Simple Messaging Program in C++</a></span></dt><dt><span class="section"><a href="ch02s02.html">2.2. A Simple Messaging Program in Python</a></span></dt><dt><span class="section"><a href="ch02s03.html">2.3. A Simple Messaging Program in .NET C#</a></span></dt><dt><span class="section"><a href="section-addresses.html">2.4. Addresses</a></span></dt><dd><dl><dt><span class="section"><a href="section-addresses.html#id579102">2.4.1. Address Strings</a></span></dt><dt><span class="section"><a href="section-addresses.html#id579146">2.4.2. Subjects</a></span></dt><dt><span class="section"><a
href="section-addresses.html#id579483">2.4.3. Address String Options</a></span></dt><dt><span class="section"><a href="section-addresses.html#section-address-string-bnf">2.4.4. Address String Grammar</a></span></dt></dl></dd><dt><span class="section"><a href="replay.html">2.5. Sender Capacity and Replay</a></span></dt><dt><span class="section"><a href="prefetch.html">2.6. Receiver Capacity (Prefetch)</a></span></dt><dt><span class="section"><a href="acknowledgements.html">2.7. Acknowledging Received Messages</a></span></dt><dt><span class="section"><a href="ch02s08.html">2.8. Receiving Messages from Multiple Sources</a></span></dt><dt><span class="section"><a href="ch02s09.html">2.9. Transactions</a></span></dt><dt><span class="section"><a href="connection-options.html">2.10. Connection Options</a></span></dt><dt><span class="section"><a href="section-Maps.html">2.11. Maps and Lists in Message Content</a></span></dt><dd><dl><dt><span class="section"><a href="section-Maps.ht
ml#section-Python-Maps">2.11.1. Qpid Maps and Lists in Python</a></span></dt><dt><span class="section"><a href="section-Maps.html#section-cpp-Maps">2.11.2. Qpid Maps and Lists in C++</a></span></dt><dt><span class="section"><a href="section-Maps.html#section-dotnet-Maps">2.11.3. Qpid Maps and Lists in .NET</a></span></dt></dl></dd><dt><span class="section"><a href="ch02s12.html">2.12. The Request / Response Pattern</a></span></dt><dt><span class="section"><a href="ch02s13.html">2.13. Performance Tips</a></span></dt><dt><span class="section"><a href="ch02s14.html">2.14. Cluster Failover</a></span></dt><dt><span class="section"><a href="ch02s15.html">2.15. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="ch02s15.html#id582183">2.15.1. Logging in C++</a></span></dt><dt><span class="section"><a href="ch02s15.html#id582225">2.15.2. Logging in Python</a></span></dt></dl></dd><dt><span class="section"><a href="section-amqp0-10-mapping.html">2.16. The AMQP 0-10 mapp
ing</a></span></dt><dd><dl><dt><span class="section"><a href="section-amqp0-10-mapping.html#section-amqp0-10-message-props">2.16.1. 0-10 Message Property Keys</a></span></dt></dl></dd><dt><span class="section"><a href="Message-Groups-Guide.html">2.17. Using Message Groups</a></span></dt><dd><dl><dt><span class="section"><a href="Message-Groups-Guide.html#messagegroups-setup">2.17.1. Creating Message Group Queues</a></span></dt><dt><span class="section"><a href="Message-Groups-Guide.html#messagegroups-sending">2.17.2. Sending Grouped Messages</a></span></dt><dt><span class="section"><a href="Message-Groups-Guide.html#messagegroups-receiving">2.17.3. Receiving Grouped Messages</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="QpidJMS.html">3. Using the Qpid JMS client</a></span></dt><dd><dl><dt><span class="section"><a href="QpidJMS.html#id582809">3.1. A Simple Messaging Program in Java JMS</a></span></dt><dt><span class="section"><a href="QpidJNDI.html">3.
2. Apache Qpid JNDI Properties for AMQP Messaging</a></span></dt><dd><dl><dt><span class="section"><a href="QpidJNDI.html#id583164">3.2.1. JNDI Properties for Apache Qpid</a></span></dt><dt><span class="section"><a href="QpidJNDI.html#section-jms-connection-url">3.2.2. Connection URLs</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s03.html">3.3. Java JMS Message Properties</a></span></dt><dt><span class="section"><a href="section-JMS-MapMessage.html">3.4. JMS MapMessage Types</a></span></dt><dt><span class="section"><a href="section-JMS-Logging.html">3.5. JMS Client Logging</a></span></dt><dt><span class="section"><a href="ch03s06.html">3.6. Configuring the JMS Client</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s06.html#client-jvm-properties">3.6.1. Qpid JVM Arguments</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="QpidWCF.html">4. Using the Qpid WCF client</a></span></dt><dd><dl><dt><span class="section"><a href="Qpid
WCF.html#id585480">4.1. XML and Binary Bindings</a></span></dt><dt><span class="section"><a href="ch04s02.html">4.2. Endpoints</a></span></dt><dt><span class="section"><a href="ch04s03.html">4.3. Message Headers</a></span></dt><dt><span class="section"><a href="ch04s04.html">4.4. Security</a></span></dt><dt><span class="section"><a href="ch04s05.html">4.5. Transactions</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch05.html">5. The .NET Binding for the C++ Messaging Client</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#id585870">5.1. .NET Binding for the C++ Messaging Client Component Architecture</a></span></dt><dt><span class="section"><a href="ch05s02.html">5.2. .NET Binding for the C++ Messaging Client Examples</a></span></dt><dt><span class="section"><a href="ch05s03.html">5.3. .NET Binding Class Mapping to Underlying C++ Messaging API</a></span></dt><dd><dl><dt><span class="section"><a href="ch05s03.html#id586404">5.3.1. .NET Binding
for the C++ Messaging API Class: Address</a></span></dt><dt><span class="section"><a href="ch05s03.html#id586994">5.3.2. .NET Binding for the C++ Messaging API Class: Connection</a></span></dt><dt><span class="section"><a href="ch05s03.html#id587620">5.3.3. .NET Binding for the C++ Messaging API Class: Duration</a></span></dt><dt><span class="section"><a href="ch05s03.html#id588031">5.3.4. .NET Binding for the C++ Messaging API Class: FailoverUpdates</a></span></dt><dt><span class="section"><a href="ch05s03.html#id588207">5.3.5. .NET Binding for the C++ Messaging API Class: Message</a></span></dt><dt><span class="section"><a href="ch05s03.html#id589359">5.3.6. .NET Binding for the C++ Messaging API Class: Receiver</a></span></dt><dt><span class="section"><a href="ch05s03.html#id589988">5.3.7. .NET Binding for the C++ Messaging API Class: Sender</a></span></dt><dt><span class="section"><a href="ch05s03.html#id590459">5.3.8. .NET Binding for the C++ Messaging API Class: Sessio
n</a></span></dt><dt><span class="section"><a href="ch05s03.html#id591395">5.3.9. .NET Binding Class: SessionReceiver</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="section-addresses.html#id579964">Address String Options</a></dt><dt>2.2. <a href="section-addresses.html#table-node-properties">Node Properties</a></dt><dt>2.3. <a href="section-addresses.html#table-link-properties">Link Properties</a></dt><dt>2.4. <a href="connection-options.html#id580931">Connection Options</a></dt><dt>2.5. <a href="section-Maps.html#tabl-Programming_in_Apache_Qpid-Qpid_Maps_in_Message_Content">Map and List Representation in Supported Languages</a></dt><dt>2.6. <a href="section-Maps.html#table-Python-Maps">Python Datatypes in Maps</a></dt><dt>2.7. <a href="section-Maps.html#table-cpp-Maps">C++ Datatypes in Maps</a></dt><dt>2.8. <a href="section-Maps.html#table-dotnet-Maps">Datatype Mapping between C++ and .NET binding<
/a></dt><dt>2.9. <a href="section-amqp0-10-mapping.html#table-amqp0-10-message-properties">Mapping to AMQP 0-10 Message Properties</a></dt><dt>3.1. <a href="QpidJNDI.html#id583174">JNDI Properties supported by Apache Qpid</a></dt><dt>3.2. <a href="QpidJNDI.html#id583301">Connection URL Properties</a></dt><dt>3.3. <a href="QpidJNDI.html#id583569">Broker List Options</a></dt><dt>3.4. <a href="ch03s03.html#id583891">Java JMS Mapping to AMQP 0-10 Message Properties</a></dt><dt>3.5. <a href="section-JMS-MapMessage.html#table-Java-Maps">Java Datatypes in Maps</a></dt><dt>3.6. <a href="ch03s06.html#id584364">Config Options For Connection Behaviour</a></dt><dt>3.7. <a href="ch03s06.html#id584465">Config Options For Session Behaviour</a></dt><dt>3.8. <a href="ch03s06.html#id584575">Config Options For Consumer Behaviour</a></dt><dt>3.9. <a href="ch03s06.html#id584704">Config Options For Producer Behaviour</a></dt><dt>3.10. <a href="ch03s06.html#id584764">Config Options For Threading</
a></dt><dt>3.11. <a href="ch03s06.html#id584839">Config Options For I/O</a></dt><dt>3.12. <a href="ch03s06.html#id585008">Config Options For Security</a></dt><dt>3.13. <a href="ch03s06.html#id585132">Config Options For Security - Standard JVM properties needed when using GSSAPI as the SASL mechanism.</a></dt><dt>3.14. <a href="ch03s06.html#id585218">Config Options For Security - Using SSL for securing connections or using EXTERNAL as the SASL mechanism.</a></dt><dt>3.15. <a href="ch03s06.html#id585332">Config Options For Security - Standard JVM properties needed when Using SSL for securing connections or using EXTERNAL as the SASL mechanism.</a></dt><dt>4.1. <a href="QpidWCF.html#id585563">WCF Binding Parameters</a></dt><dt>5.1. <a href="ch05.html#table-Dotnet-Binding-Component-Architecture">.NET Binding for the C++ Messaging Client Component Architecture</a></dt><dt>5.2. <a href="ch05s02.html#table-Dotnet-Binding-Example-Client-Server">Example : Client - Server</a></dt><dt>
5.3. <a href="ch05s02.html#table-Dotnet-Binding-Example-MapSender-MapReceiver">Example : Map Sender â Map Receiver</a></dt><dt>5.4. <a href="ch05s02.html#table-Dotnet-Binding-Example-Spout-Drain">Example : Spout - Drain</a></dt><dt>5.5. <a href="ch05s02.html#table-Dotnet-Binding-Example-CallbackSender-CallbackReceiver">Example : Map Callback Sender â Map Callback Receiver</a></dt><dt>5.6. <a href="ch05s02.html#table-Dotnet-Binding-Example-DeclareQueues">Example - Declare Queues</a></dt><dt>5.7. <a href="ch05s02.html#table-Dotnet-Binding-Example-DirectSender-DirectReceiver">Example: Direct Sender - Direct Receiver</a></dt><dt>5.8. <a href="ch05s02.html#table-Dotnet-Binding-Example-Helloworld">Example: Hello World</a></dt><dt>5.9. <a href="ch05s03.html#table-Dotnet-Binding-Address">.NET Binding for the C++ Messaging API Class: Address</a></dt><dt>5.10. <a href="ch05s03.html#table-Dotnet-Binding-Connection">.NET Binding for the C++ Messaging API Class: Connection</a><
/dt><dt>5.11. <a href="ch05s03.html#table-Dotnet-Binding-Duration">.NET Binding for the C++ Messaging API Class: Duration</a></dt><dt>5.12. <a href="ch05s03.html#table-Dotnet-Binding-FailoverUpdates">.NET Binding for the C++ Messaging API Class: FailoverUpdates</a></dt><dt>5.13. <a href="ch05s03.html#table-Dotnet-Binding-Message">.NET Binding for the C++ Messaging API Class: Message</a></dt><dt>5.14. <a href="ch05s03.html#table-Dotnet-Binding-Receiver">.NET Binding for the C++ Messaging API Class: Receiver</a></dt><dt>5.15. <a href="ch05s03.html#table-Dotnet-Binding-Sender">.NET Binding for the C++ Messaging API Class: Sender</a></dt><dt>5.16. <a href="ch05s03.html#table-Dotnet-Binding-Session">.NET Binding for the C++ Messaging API Class: Session</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>2.1. <a href="ch02.html#id533748">"Hello world!" in C++</a></dt><dt>2.2. <a href="ch02s02.html#id532989">"Hello world!" in Python</a></dt><dt>2.
3. <a href="ch02s03.html#id578585">"Hello world!" in .NET C#</a></dt><dt>2.4. <a href="section-addresses.html#id578893">Queues</a></dt><dt>2.5. <a href="section-addresses.html#id578968">Topics</a></dt><dt>2.6. <a href="section-addresses.html#id579178">Using subjects</a></dt><dt>2.7. <a href="section-addresses.html#id579352">Subjects with multi-word keys</a></dt><dt>2.8. <a href="section-addresses.html#id579598">Assertions on Nodes</a></dt><dt>2.9. <a href="section-addresses.html#id579678">Creating a Queue Automatically</a></dt><dt>2.10. <a href="section-addresses.html#id579747">Browsing a Queue</a></dt><dt>2.11. <a href="section-addresses.html#id579859">Using the XML Exchange</a></dt><dt>2.12. <a href="ch02s08.html#id580727">Receiving Messages from Multiple Sources</a></dt><dt>2.13. <a href="ch02s09.html#id580794">Transactions</a></dt><dt>2.14. <a href="connection-options.html#id580838">Specifying Connection Options in C++, Python, and .NET</a></dt><dt>2.15. <a href="section
-Maps.html#id581400">Sending Qpid Maps and Lists in Python</a></dt><dt>2.16. <a href="section-Maps.html#id581558">Sending Qpid Maps and Lists in C++</a></dt><dt>2.17. <a href="section-Maps.html#id581753">Sending Qpid Maps and Lists in .NET C#</a></dt><dt>2.18. <a href="ch02s12.html#id581963">Request / Response Applications in C++</a></dt><dt>2.19. <a href="ch02s14.html#id582128">Tracking cluster membership</a></dt><dt>2.20. <a href="section-amqp0-10-mapping.html#id582751">Accessing the AMQP 0-10 Message Timestamp in Python</a></dt><dt>2.21. <a href="section-amqp0-10-mapping.html#id582771">Accessing the AMQP 0-10 Message Timestamp in C++</a></dt><dt>2.22. <a href="Message-Groups-Guide.html#id580353">Message Group Queue Creation - Python</a></dt><dt>2.23. <a href="Message-Groups-Guide.html#id580368">Message Group Queue Creation - C++</a></dt><dt>2.24. <a href="Message-Groups-Guide.html#id580383">Message Group Queue Creation - Java</a></dt><dt>2.25. <a href="Message-Groups-Guid
e.html#id532214">Sending Grouped Messages - Python</a></dt><dt>2.26. <a href="Message-Groups-Guide.html#id532230">Sending Grouped Messages - C++</a></dt><dt>2.27. <a href="Message-Groups-Guide.html#id532247">Sending Grouped Messages - Java</a></dt><dt>3.1. <a href="QpidJMS.html#id582827">"Hello world!" in Java</a></dt><dt>3.2. <a href="QpidJMS.html#id583069">JNDI Properties File for "Hello world!" example</a></dt><dt>3.3. <a href="QpidJNDI.html#id583146">JNDI Properties File</a></dt><dt>3.4. <a href="QpidJNDI.html#id583526">Broker Lists</a></dt><dt>3.5. <a href="section-JMS-MapMessage.html#id584056">Sending a Java JMS MapMessage</a></dt><dt>3.6. <a href="section-JMS-Logging.html#id584252">log4j Logging Properties</a></dt><dt>4.1. <a href="QpidWCF.html#id585497">Traditional service model "Hello world!" example</a></dt><dt>4.2. <a href="QpidWCF.html#id585524">Binary "Hello world!" example using the channel model</a></dt></dl></div></div><div class="navfooter"><hr><table width
="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch01.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-Logging.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-Logging.html?rev=1310030&r1=1310029&r2=1310030&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-Logging.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-Logging.html Thu Apr 5 19:34:23 2012
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.5. JMS Client Logging</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="QpidJMS.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="section-JMS-MapMessage.html" title="3.4. JMS MapMessage Types"><link rel="next" href="ch03s06.html" title="3.6. Configuring the JMS Client"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.5. JMS Client Logging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="section-JMS-MapMessage.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Using the Qpid JMS client</th><td widt
h="20%" align="right"> <a accesskey="n" href="ch03s06.html">Next</a></td></tr></table><hr></div><div class="section" title="3.5. JMS Client Logging"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-JMS-Logging"></a>3.5. JMS Client Logging</h2></div></div></div><p>The JMS Client logging is handled using the Simple Logging Facade for Java (<a class="ulink" href="http://www.slf4j.org/" target="_top">SLF4J</a>). As the name implies, slf4j is a facade that delegates to other logging systems like log4j or JDK 1.4 logging. For more information on how to configure slf4j for specific logging systems, please consult the slf4j documentation.</p><p>When using the log4j binding, please set the log level for org.apache.qpid explicitly. Otherwise log4j will default to DEBUG which will degrade performance considerably due to excessive logging. The recommended logging level for production is <code class="literal">WARN</code>.</p><p>The followin
g example shows the logging properties used to configure client logging for slf4j using the log4j binding. These properties can be placed in a log4j.properties file and placed in the <code class="varname">CLASSPATH</code>, or they can be set explicitly using the <code class="literal">-Dlog4j.configuration</code> property.</p><div class="example"><a name="id386791"></a><p class="title"><b>Example 3.6. log4j Logging Properties</b></p><div class="example-contents"><pre class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.5. JMS Client Logging</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="QpidJMS.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="section-JMS-MapMessage.html" title="3.4. JMS MapMessage Types"><link rel="next" href="ch03s06.html" title="3.6. Configuring the JMS Client"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.5. JMS Client Logging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="section-JMS-MapMessage.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Using the Qpid JMS client</th><td widt
h="20%" align="right"> <a accesskey="n" href="ch03s06.html">Next</a></td></tr></table><hr></div><div class="section" title="3.5. JMS Client Logging"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-JMS-Logging"></a>3.5. JMS Client Logging</h2></div></div></div><p>The JMS Client logging is handled using the Simple Logging Facade for Java (<a class="ulink" href="http://www.slf4j.org/" target="_top">SLF4J</a>). As the name implies, slf4j is a facade that delegates to other logging systems like log4j or JDK 1.4 logging. For more information on how to configure slf4j for specific logging systems, please consult the slf4j documentation.</p><p>When using the log4j binding, please set the log level for org.apache.qpid explicitly. Otherwise log4j will default to DEBUG which will degrade performance considerably due to excessive logging. The recommended logging level for production is <code class="literal">WARN</code>.</p><p>The followin
g example shows the logging properties used to configure client logging for slf4j using the log4j binding. These properties can be placed in a log4j.properties file and placed in the <code class="varname">CLASSPATH</code>, or they can be set explicitly using the <code class="literal">-Dlog4j.configuration</code> property.</p><div class="example"><a name="id584252"></a><p class="title"><b>Example 3.6. log4j Logging Properties</b></p><div class="example-contents"><pre class="programlisting">
log4j.logger.org.apache.qpid=WARN, console
log4j.additivity.org.apache.qpid=false
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-MapMessage.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-MapMessage.html?rev=1310030&r1=1310029&r2=1310030&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-MapMessage.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-MapMessage.html Thu Apr 5 19:34:23 2012
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.4. JMS MapMessage Types</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="QpidJMS.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s03.html" title="3.3. Java JMS Message Properties"><link rel="next" href="section-JMS-Logging.html" title="3.5. JMS Client Logging"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.4. JMS MapMessage Types</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s03.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Using the Qpid JMS client</th><td width="20%" align="
right"> <a accesskey="n" href="section-JMS-Logging.html">Next</a></td></tr></table><hr></div><div class="section" title="3.4. JMS MapMessage Types"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-JMS-MapMessage"></a>3.4. JMS MapMessage Types</h2></div></div></div><p>Qpid supports the Java JMS <code class="classname">MapMessage</code> interface, which provides support for maps in messages. The following code shows how to send a <code class="classname">MapMessage</code> in Java JMS.</p><div class="example"><a name="id386595"></a><p class="title"><b>Example 3.5. Sending a Java JMS MapMessage</b></p><div class="example-contents"><pre class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.4. JMS MapMessage Types</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="QpidJMS.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s03.html" title="3.3. Java JMS Message Properties"><link rel="next" href="section-JMS-Logging.html" title="3.5. JMS Client Logging"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.4. JMS MapMessage Types</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s03.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Using the Qpid JMS client</th><td width="20%" align="
right"> <a accesskey="n" href="section-JMS-Logging.html">Next</a></td></tr></table><hr></div><div class="section" title="3.4. JMS MapMessage Types"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-JMS-MapMessage"></a>3.4. JMS MapMessage Types</h2></div></div></div><p>Qpid supports the Java JMS <code class="classname">MapMessage</code> interface, which provides support for maps in messages. The following code shows how to send a <code class="classname">MapMessage</code> in Java JMS.</p><div class="example"><a name="id584056"></a><p class="title"><b>Example 3.5. Sending a Java JMS MapMessage</b></p><div class="example-contents"><pre class="programlisting">
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
@@ -45,4 +45,4 @@
m.setObject("specs",specs);
producer.send(m);
- </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent in a <code class="classname">MapMessage</code>, and the corresponding datatypes that will be received by clients in Python or C++.</p><div class="table"><a name="table-Java-Maps"></a><p class="title"><b>Table 3.5. Java Datatypes in Maps</b></p><div class="table-contents"><table summary="Java Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Java Datatype</th><th>â Python</th><th>â C++</th></tr></thead><tbody><tr><td>boolean</td><td>bool</td><td>bool</td></tr><tr><td>short</td><td>int | long</td><td>int16</td></tr><tr><td>int</td><td>int | long</td><td>int32</td></tr><tr><td>long</td><td>int | long</td><td>int64</td></tr><tr><td>float</td><td>float</td><td>float</td></tr><tr><td>double</td><td>float</td><td>double</td></tr><tr><td>java.lang.String</td><td>unicode</td><td>std::string</td></tr><tr><td>java.util.UUID</td><td>uuid
</td><td>qpid::types::Uuid</td></tr><tr><td>java.util.Map<sup>[<a name="id386726" href="#ftn.id386726" class="footnote">a</a>]</sup></td><td>dict</td><td>Variant::Map</td></tr><tr><td>java.util.List</td><td>list</td><td>Variant::List</td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div class="footnote"><p><sup>[<a id="ftn.id386726" href="#id386726" class="para">a</a>] </sup>In Qpid, maps can nest. This goes beyond the functionality required by the JMS specification.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="QpidJMS.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="section-JMS-Logging.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.3. Java JMS Message PropertiesÂ
</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.5. JMS Client Logging</td></tr></table></div></body></html>
+ </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent in a <code class="classname">MapMessage</code>, and the corresponding datatypes that will be received by clients in Python or C++.</p><div class="table"><a name="table-Java-Maps"></a><p class="title"><b>Table 3.5. Java Datatypes in Maps</b></p><div class="table-contents"><table summary="Java Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Java Datatype</th><th>â Python</th><th>â C++</th></tr></thead><tbody><tr><td>boolean</td><td>bool</td><td>bool</td></tr><tr><td>short</td><td>int | long</td><td>int16</td></tr><tr><td>int</td><td>int | long</td><td>int32</td></tr><tr><td>long</td><td>int | long</td><td>int64</td></tr><tr><td>float</td><td>float</td><td>float</td></tr><tr><td>double</td><td>float</td><td>double</td></tr><tr><td>java.lang.String</td><td>unicode</td><td>std::string</td></tr><tr><td>java.util.UUID</td><td>uuid
</td><td>qpid::types::Uuid</td></tr><tr><td>java.util.Map<sup>[<a name="id584188" href="#ftn.id584188" class="footnote">a</a>]</sup></td><td>dict</td><td>Variant::Map</td></tr><tr><td>java.util.List</td><td>list</td><td>Variant::List</td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div class="footnote"><p><sup>[<a id="ftn.id584188" href="#id584188" class="para">a</a>] </sup>In Qpid, maps can nest. This goes beyond the functionality required by the JMS specification.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="QpidJMS.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="section-JMS-Logging.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.3. Java JMS Message PropertiesÂ
</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.5. JMS Client Logging</td></tr></table></div></body></html>
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-Maps.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-Maps.html?rev=1310030&r1=1310029&r2=1310030&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-Maps.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-Maps.html Thu Apr 5 19:34:23 2012
@@ -2,9 +2,9 @@
languages and platforms, using the native datatypes of each
programming language.</p><p>The Qpid Messaging API supports <code class="classname">map</code> and <code class="classname">list</code> in message content.
- <sup>[<a name="id383789" href="#ftn.id383789" class="footnote">9</a>]</sup>
+ <sup>[<a name="id581250" href="#ftn.id581250" class="footnote">9</a>]</sup>
- <sup>[<a name="id383794" href="#ftn.id383794" class="footnote">10</a>]</sup>
+ <sup>[<a name="id581255" href="#ftn.id581255" class="footnote">10</a>]</sup>
Specific language support for <code class="classname">map</code> and <code class="classname">list</code> objects are shown in the following table.
</p><div class="table"><a name="tabl-Programming_in_Apache_Qpid-Qpid_Maps_in_Message_Content"></a><p class="title"><b>Table 2.5. Map and List Representation in Supported Languages</b></p><div class="table-contents"><table summary="Map and List Representation in Supported Languages" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Language</th><th>map</th><th>list</th></tr></thead><tbody><tr><td>Python</td><td><code class="classname">dict</code></td><td><code class="classname">list</code></td></tr><tr><td>C++</td><td><code class="classname">Variant::Map</code></td><td><code class="classname">Variant::List</code></td></tr><tr><td>Java</td><td><code class="classname">MapMessage</code></td><td><code class="classname"> </code></td></tr><tr><td>.NET</td><td><code class="classname">Dictionary<string, object></code></td><td><code class="classname">Collection<object></code></td></tr></tbody></table></div></div><br class="table-break"><p>
In all languages, messages are encoded using AMQP's portable datatypes.
@@ -12,7 +12,7 @@
languages, the simplest way to provide portable messages is to
rely on maps, lists, strings, 64 bit signed integers, and
doubles for messages that need to be exchanged across languages
- and platforms.</p></div><div class="section" title="2.11.1. Qpid Maps and Lists in Python"><div class="titlepage"><div><div><h3 class="title"><a name="section-Python-Maps"></a>2.11.1. Qpid Maps and Lists in Python</h3></div></div></div><p>In Python, Qpid supports the <code class="classname">dict</code> and <code class="classname">list</code> types directly in message content. The following code shows how to send these structures in a message:</p><div class="example"><a name="id383939"></a><p class="title"><b>Example 2.15. Sending Qpid Maps and Lists in Python</b></p><div class="example-contents"><pre class="programlisting">
+ and platforms.</p></div><div class="section" title="2.11.1. Qpid Maps and Lists in Python"><div class="titlepage"><div><div><h3 class="title"><a name="section-Python-Maps"></a>2.11.1. Qpid Maps and Lists in Python</h3></div></div></div><p>In Python, Qpid supports the <code class="classname">dict</code> and <code class="classname">list</code> types directly in message content. The following code shows how to send these structures in a message:</p><div class="example"><a name="id581400"></a><p class="title"><b>Example 2.15. Sending Qpid Maps and Lists in Python</b></p><div class="example-contents"><pre class="programlisting">
from qpid.messaging import *
# !!! SNIP !!!
@@ -30,7 +30,7 @@
<code class="classname">Variant::Map</code> and
<code class="classname">Variant::List</code> types, which can be
encoded into message content. The following code shows how to
- send these structures in a message:</p><div class="example"><a name="id384097"></a><p class="title"><b>Example 2.16. Sending Qpid Maps and Lists in C++</b></p><div class="example-contents"><pre class="programlisting">
+ send these structures in a message:</p><div class="example"><a name="id581558"></a><p class="title"><b>Example 2.16. Sending Qpid Maps and Lists in C++</b></p><div class="example-contents"><pre class="programlisting">
using namespace qpid::types;
// !!! SNIP !!!
@@ -81,7 +81,7 @@
The .NET binding for the Qpid Messaging API binds .NET managed data types
to C++ <code class="classname">Variant</code> data types. The following code shows how to
send Map and List structures in a message:
- </p><div class="example"><a name="id384292"></a><p class="title"><b>Example 2.17. Sending Qpid Maps and Lists in .NET C#</b></p><div class="example-contents"><pre class="programlisting">
+ </p><div class="example"><a name="id581753"></a><p class="title"><b>Example 2.17. Sending Qpid Maps and Lists in .NET C#</b></p><div class="example-contents"><pre class="programlisting">
using System;
using Org.Apache.Qpid.Messaging;
@@ -151,7 +151,7 @@
</p><div class="table"><a name="table-dotnet-Maps"></a><p class="title"><b>Table 2.8. Datatype Mapping between C++ and .NET binding</b></p><div class="table-contents"><table summary="Datatype Mapping between C++ and .NET binding" border="1"><colgroup><col><col></colgroup><thead><tr><th>C++ Datatype</th><th>â .NET binding</th></tr></thead><tbody><tr><td>void</td><td>nullptr</td></tr><tr><td>bool</td><td>bool</td></tr><tr><td>uint8</td><td>byte</td></tr><tr><td>uint16</td><td>UInt16</td></tr><tr><td>uint32</td><td>UInt32</td></tr><tr><td>uint64</td><td>UInt64</td></tr><tr><td>uint8</td><td>char</td></tr><tr><td>int16</td><td>Int16</td></tr><tr><td>int32</td><td>Int32</td></tr><tr><td>int64</td><td>Int64</td></tr><tr><td>float</td><td>Single</td></tr><tr><td>double</td><td>Double</td></tr><tr><td>string</td><td>string
<sup>[<a name="callout-dotnet-string" href="#ftn.callout-dotnet-string" class="footnote">a</a>]</sup></td></tr><tr><td>qpid::types::Uuid</td><td>Guid</td></tr><tr><td>Variant::Map</td><td>Dictionary<string, object>
<sup>[<a href="section-Maps.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr><tr><td>Variant::List</td><td>Collection<object>
- <sup>[<a href="section-Maps.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a id="ftn.callout-dotnet-string" href="#callout-dotnet-string" class="para">a</a>] </sup>Strings are currently interpreted only with UTF-8 encoding.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.id383789" href="#id383789" class="para">9</a>] </sup>Unlike JMS, there is not a specific message type for
- map messages.</p></div><div class="footnote"><p><sup>[<a id="ftn.id383794" href="#id383794" class="para">10</a>] </sup>
+ <sup>[<a href="section-Maps.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a id="ftn.callout-dotnet-string" href="#callout-dotnet-string" class="para">a</a>] </sup>Strings are currently interpreted only with UTF-8 encoding.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.id581250" href="#id581250" class="para">9</a>] </sup>Unlike JMS, there is not a specific message type for
+ map messages.</p></div><div class="footnote"><p><sup>[<a id="ftn.id581255" href="#id581255" class="para">10</a>] </sup>
Note that the Qpid JMS client supports MapMessages whose values can be nested maps or lists. This is not standard JMS behaviour.
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="connection-options.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s12.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.10. Connection Options </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.12. The Request / Response Pattern</td></tr></table></div></body></html>
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-addresses.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-addresses.html?rev=1310030&r1=1310029&r2=1310030&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-addresses.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-addresses.html Thu Apr 5 19:34:23 2012
@@ -1,7 +1,7 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.4. Addresses</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch02.html" title="Chapter 2. Using the Qpid Messaging API"><link rel="prev" href="ch02s03.html" title="2.3. A Simple Messaging Program in .NET C#"><link rel="next" href="replay.html" title="2.5. Sender Capacity and Replay"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.4. Addresses</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s03.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td width="20%" align="right"> <a
accesskey="n" href="replay.html">Next</a></td></tr></table><hr></div><div class="section" title="2.4. Addresses"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-addresses"></a>2.4. Addresses</h2></div></div></div><p>An <em class="firstterm">address</em> is the name of a message
target or message source.
- <sup>[<a name="id381307" href="#ftn.id381307" class="footnote">2</a>]</sup>
+ <sup>[<a name="id578768" href="#ftn.id578768" class="footnote">2</a>]</sup>
The methods that create senders and receivers require an
address. The details of sending to a particular target or
@@ -12,22 +12,22 @@
Qpid Messaging API recognises two kinds of nodes,
<em class="firstterm">queues</em> and <em class="firstterm">topics</em>
- <sup>[<a name="id381334" href="#ftn.id381334" class="footnote">3</a>]</sup>.
+ <sup>[<a name="id578795" href="#ftn.id578795" class="footnote">3</a>]</sup>.
A queue stores each message until it has been received and
acknowledged, and only one receiver can receive a given message
- <sup>[<a name="id381355" href="#ftn.id381355" class="footnote">4</a>]</sup>.
+ <sup>[<a name="id578816" href="#ftn.id578816" class="footnote">4</a>]</sup>.
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,
- <sup>[<a name="id381368" href="#ftn.id381368" class="footnote">5</a>]</sup>
+ <sup>[<a name="id578829" href="#ftn.id578829" class="footnote">5</a>]</sup>
queues map to AMQP queues, and topics map to AMQP exchanges.
- <sup>[<a name="id381374" href="#ftn.id381374" class="footnote">6</a>]</sup>
+ <sup>[<a name="id578835" href="#ftn.id578835" class="footnote">6</a>]</sup>
</p><p>In the rest of this tutorial, we present many examples
using two programs that take an address as a command line
parameter. <span class="command"><strong>spout</strong></span> sends messages to the
@@ -39,13 +39,13 @@
configure behaviorâuse the <span class="command"><strong>-h</strong></span> option
for documentation on these options.
- <sup>[<a name="id381404" href="#ftn.id381404" class="footnote">7</a>]</sup>
+ <sup>[<a name="id578865" href="#ftn.id578865" class="footnote">7</a>]</sup>
The examples in this tutorial also use the
<span class="command"><strong>qpid-config</strong></span> utility to configure AMQP 0-10
queues and exchanges on a Qpid broker.
- </p><div class="example"><a name="id381432"></a><p class="title"><b>Example 2.4. Queues</b></p><div class="example-contents"><p>Create a queue with <span class="command"><strong>qpid-config</strong></span>, send a message using
+ </p><div class="example"><a name="id578893"></a><p class="title"><b>Example 2.4. Queues</b></p><div class="example-contents"><p>Create a queue with <span class="command"><strong>qpid-config</strong></span>, send a message using
<span class="command"><strong>spout</strong></span>, and read it using <span class="command"><strong>drain</strong></span>:</p><pre class="screen">
$ qpid-config add queue hello-world
$ ./spout hello-world
@@ -58,7 +58,7 @@
<span class="command"><strong>drain</strong></span> one more time, no messages will be retrieved.</p><pre class="screen">
$ ./drain hello-world
$
- </pre></div></div><br class="example-break"><div class="example"><a name="id381506"></a><p class="title"><b>Example 2.5. Topics</b></p><div class="example-contents"><p>This example is similar to the previous example, but it
+ </pre></div></div><br class="example-break"><div class="example"><a name="id578968"></a><p class="title"><b>Example 2.5. Topics</b></p><div class="example-contents"><p>This example is similar to the previous example, but it
uses a topic instead of a queue.</p><p>First, use <span class="command"><strong>qpid-config</strong></span> to remove the queue
and create an exchange with the same name:</p><pre class="screen">
$ qpid-config del queue hello-world
@@ -85,7 +85,7 @@
Message(properties={spout-id:7da2d27d-93e6-4803-8a61-536d87b8d93f:0}, content='')
</pre><p>You can run <span class="command"><strong>drain</strong></span> in several separate
windows; each creates a subscription for the exchange, and
- each receives all messages sent to the exchange.</p></div></div><br class="example-break"><div class="section" title="2.4.1. Address Strings"><div class="titlepage"><div><div><h3 class="title"><a name="id381641"></a>2.4.1. Address Strings</h3></div></div></div><p>So far, our examples have used address strings that
+ each receives all messages sent to the exchange.</p></div></div><br class="example-break"><div class="section" title="2.4.1. Address Strings"><div class="titlepage"><div><div><h3 class="title"><a name="id579102"></a>2.4.1. Address Strings</h3></div></div></div><p>So far, our examples have used address strings that
contain only the name of a node. An <em class="firstterm">address
string</em> can also contain a
<em class="firstterm">subject</em> and
@@ -97,7 +97,7 @@
maps, or lists. A complete BNF for address strings appears in
<a class="xref" href="section-addresses.html#section-address-string-bnf" title="2.4.4. Address String Grammar">Section 2.4.4, âAddress String Grammarâ</a>.</p><p>So far, the address strings in this tutorial have only
used simple names. The following sections show how to use
- subjects and options.</p></div><div class="section" title="2.4.2. Subjects"><div class="titlepage"><div><div><h3 class="title"><a name="id381684"></a>2.4.2. Subjects</h3></div></div></div><p>Every message has a property called
+ subjects and options.</p></div><div class="section" title="2.4.2. Subjects"><div class="titlepage"><div><div><h3 class="title"><a name="id579146"></a>2.4.2. Subjects</h3></div></div></div><p>Every message has a property called
<em class="firstterm">subject</em>, 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
@@ -116,7 +116,7 @@
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.
- </p></div><div class="example"><a name="id381717"></a><p class="title"><b>Example 2.6. Using subjects</b></p><div class="example-contents"><p>In this example we show how subjects affect message
+ </p></div><div class="example"><a name="id579178"></a><p class="title"><b>Example 2.6. Using subjects</b></p><div class="example-contents"><p>In this example we show how subjects affect message
flow.</p><p>First, let's use <span class="command"><strong>qpid-config</strong></span> to create a topic exchange.</p><pre class="screen">
$ qpid-config add exchange topic news-service
</pre><p>Now we use drain to receive messages from <code class="literal">news-service</code> that match the subject <code class="literal">sports</code>.</p><p><span class="emphasis"><em>First Window:</em></span></p><pre class="screen">
@@ -152,7 +152,7 @@
<code class="literal">usa.news</code>; if it is
<code class="literal">europe.#</code>, it matches messages with subjects
like <code class="literal">europe.news</code> or
- <code class="literal">europe.pseudo.news</code>.</p><div class="example"><a name="id381890"></a><p class="title"><b>Example 2.7. Subjects with multi-word keys</b></p><div class="example-contents"><p>This example uses drain and spout to demonstrate the
+ <code class="literal">europe.pseudo.news</code>.</p><div class="example"><a name="id579352"></a><p class="title"><b>Example 2.7. Subjects with multi-word keys</b></p><div class="example-contents"><p>This example uses drain and spout to demonstrate the
use of subjects with two-word keys.</p><p>Let's use <span class="command"><strong>drain</strong></span> with the subject
<code class="literal">*.news</code> to listen for messages in which
the second word of the key is
@@ -187,7 +187,7 @@
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='')
- </pre></div></div><br class="example-break"></div><div class="section" title="2.4.3. Address String Options"><div class="titlepage"><div><div><h3 class="title"><a name="id382022"></a>2.4.3. Address String Options</h3></div></div></div><p>
+ </pre></div></div><br class="example-break"></div><div class="section" title="2.4.3. Address String Options"><div class="titlepage"><div><div><h3 class="title"><a name="id579483"></a>2.4.3. Address String Options</h3></div></div></div><p>
The options in an address string can contain additional
information for the senders or receivers created for it,
including:
@@ -223,11 +223,11 @@
Let's use some examples to show how these different kinds of
address string options affect the behavior of senders and
receives.
- </p><div class="section" title="2.4.3.1. assert"><div class="titlepage"><div><div><h4 class="title"><a name="id382122"></a>2.4.3.1. assert</h4></div></div></div><p>
+ </p><div class="section" title="2.4.3.1. assert"><div class="titlepage"><div><div><h4 class="title"><a name="id579583"></a>2.4.3.1. assert</h4></div></div></div><p>
In this section, we use the <code class="literal">assert</code> option
to ensure that the address resolves to a node of the required
type.
- </p><div class="example"><a name="id382137"></a><p class="title"><b>Example 2.8. Assertions on Nodes</b></p><div class="example-contents"><p>Let's use <span class="command"><strong>qpid-config</strong></span> to create a
+ </p><div class="example"><a name="id579598"></a><p class="title"><b>Example 2.8. Assertions on Nodes</b></p><div class="example-contents"><p>Let's use <span class="command"><strong>qpid-config</strong></span> to create a
queue and a topic.</p><pre class="screen">
$ qpid-config add queue my-queue
$ qpid-config add exchange topic my-topic
@@ -252,15 +252,15 @@
Queue my-topic does not exist
</pre></div></div><br class="example-break"><p>Now let's use the <code class="literal">create</code> option to
create the queue <code class="literal">xoxox</code> if it does not already
- exist:</p></div><div class="section" title="2.4.3.2. create"><div class="titlepage"><div><div><h4 class="title"><a name="id382201"></a>2.4.3.2. create</h4></div></div></div><p>In previous examples, we created the queue before
+ exist:</p></div><div class="section" title="2.4.3.2. create"><div class="titlepage"><div><div><h4 class="title"><a name="id579663"></a>2.4.3.2. create</h4></div></div></div><p>In previous examples, we created the queue before
listening for messages on it. Using <code class="literal">create:
always</code>, the queue is automatically created if it
- does not exist.</p><div class="example"><a name="id382217"></a><p class="title"><b>Example 2.9. Creating a Queue Automatically</b></p><div class="example-contents"><p><span class="emphasis"><em>First Window:</em></span></p><pre class="screen">$ ./drain -t 30 "xoxox ; {create: always}"</pre><p>Now we can send messages to this queue:</p><p><span class="emphasis"><em>Second Window:</em></span></p><pre class="screen">$ ./spout "xoxox ; {create: always}"</pre><p>Returning to the first window, we see that <span class="command"><strong>drain</strong></span> has received this message:</p><pre class="screen">Message(properties={spout-id:1a1a3842-1a8b-4f88-8940-b4096e615a7d:0}, content='')</pre></div></div><br class="example-break"><p>The details of the node thus created can be controlled by further options within the node. See <a class="xref" href="section-addresses.html#table-node-properties" title="Table 2.2. Node Properties">Table 2.2, âNode Propertiesâ
</a> for details.</p></div><div class="section" title="2.4.3.3. browse"><div class="titlepage"><div><div><h4 class="title"><a name="id382269"></a>2.4.3.3. browse</h4></div></div></div><p>Some options specify message transfer semantics; for
+ does not exist.</p><div class="example"><a name="id579678"></a><p class="title"><b>Example 2.9. Creating a Queue Automatically</b></p><div class="example-contents"><p><span class="emphasis"><em>First Window:</em></span></p><pre class="screen">$ ./drain -t 30 "xoxox ; {create: always}"</pre><p>Now we can send messages to this queue:</p><p><span class="emphasis"><em>Second Window:</em></span></p><pre class="screen">$ ./spout "xoxox ; {create: always}"</pre><p>Returning to the first window, we see that <span class="command"><strong>drain</strong></span> has received this message:</p><pre class="screen">Message(properties={spout-id:1a1a3842-1a8b-4f88-8940-b4096e615a7d:0}, content='')</pre></div></div><br class="example-break"><p>The details of the node thus created can be controlled by further options within the node. See <a class="xref" href="section-addresses.html#table-node-properties" title="Table 2.2. Node Properties">Table 2.2, âNode Propertiesâ
</a> for details.</p></div><div class="section" title="2.4.3.3. browse"><div class="titlepage"><div><div><h4 class="title"><a name="id579730"></a>2.4.3.3. browse</h4></div></div></div><p>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
<code class="literal">browse</code> option to receive messages without
- removing them from a queue.</p><div class="example"><a name="id382285"></a><p class="title"><b>Example 2.10. Browsing a Queue</b></p><div class="example-contents"><p>
+ removing them from a queue.</p><div class="example"><a name="id579747"></a><p class="title"><b>Example 2.10. Browsing a Queue</b></p><div class="example-contents"><p>
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 @@
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')
- </pre></div></div><br class="example-break"></div><div class="section" title="2.4.3.4. x-bindings"><div class="titlepage"><div><div><h4 class="title"><a name="id382328"></a>2.4.3.4. x-bindings</h4></div></div></div><p>Greater control over the AMQP 0-10 binding process can
+ </pre></div></div><br class="example-break"></div><div class="section" title="2.4.3.4. x-bindings"><div class="titlepage"><div><div><h4 class="title"><a name="id579789"></a>2.4.3.4. x-bindings</h4></div></div></div><p>Greater control over the AMQP 0-10 binding process can
be achieved by including an <code class="literal">x-bindings</code>
option in an address string.
@@ -308,7 +308,7 @@
</pre><p>When using longer queries with <span class="command"><strong>drain</strong></span>,
it is often useful to place the query in a file, and use
<span class="command"><strong>cat</strong></span> in the command line. We do this in the
- following example.</p><div class="example"><a name="id382398"></a><p class="title"><b>Example 2.11. Using the XML Exchange</b></p><div class="example-contents"><p>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:</p><pre class="programlisting">
+ following example.</p><div class="example"><a name="id579859"></a><p class="title"><b>Example 2.11. Using the XML Exchange</b></p><div class="example-contents"><p>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:</p><pre class="programlisting">
let $w := ./weather
return $w/station = 'Raleigh-Durham International Airport (KRDU)'
@@ -337,7 +337,7 @@
<temperature_f>40</temperature_f>
<dewpoint>35</dewpoint>
</weather>')
- </pre></div></div><br class="example-break"></div><div class="section" title="2.4.3.5. Address String Options - Reference"><div class="titlepage"><div><div><h4 class="title"><a name="id382498"></a>2.4.3.5. Address String Options - Reference</h4></div></div></div><div class="table"><a name="id382503"></a><p class="title"><b>Table 2.1. Address String Options</b></p><div class="table-contents"><table summary="Address String Options" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>option</th><th>value</th><th>semantics</th></tr></thead><tbody><tr><td>
+ </pre></div></div><br class="example-break"></div><div class="section" title="2.4.3.5. Address String Options - Reference"><div class="titlepage"><div><div><h4 class="title"><a name="id579959"></a>2.4.3.5. Address String Options - Reference</h4></div></div></div><div class="table"><a name="id579964"></a><p class="title"><b>Table 2.1. Address String Options</b></p><div class="table-contents"><table summary="Address String Options" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>option</th><th>value</th><th>semantics</th></tr></thead><tbody><tr><td>
assert
</td><td>
one of: always, never, sender or receiver
@@ -454,7 +454,7 @@
that a message is not lost, and is delivered precisely
once. Currently only <code class="literal">unreliable</code>
and <code class="literal">at-least-once</code> are supported.
- <sup>[<a name="id382870" href="#ftn.id382870" class="footnote">a</a>]</sup>
+ <sup>[<a name="id580331" href="#ftn.id580331" class="footnote">a</a>]</sup>
</td></tr><tr><td>
durable
</td><td>
@@ -489,7 +489,7 @@
independent of the create option. They are considered
logically part of the linking process rather than of
node creation.
- </td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div class="footnote"><p><sup>[<a id="ftn.id382870" href="#id382870" class="para">a</a>] </sup>If at-most-once is requested,
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div class="footnote"><p><sup>[<a id="ftn.id580331" href="#id580331" class="para">a</a>] </sup>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 @@
</pre><div class="itemizedlist" title="Create, Delete, and Assert Policies"><p class="title"><b>Create, Delete, and Assert Policies</b></p><p>The create, delete, and assert policies specify who should
perfom the associated action:</p><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>always</em></span>: the action is performed by any messaging client</p></li><li class="listitem"><p><span class="emphasis"><em>sender</em></span>: the action is only performed by a sender</p></li><li class="listitem"><p><span class="emphasis"><em>receiver</em></span>: the action is only performed by a receiver</p></li><li class="listitem"><p><span class="emphasis"><em>never</em></span>: the action is never performed (this is the default)</p></li></ul></div><div class="itemizedlist" title="Node-Type"><p class="title"><b>Node-Type</b></p><p>The node-type is one of:</p><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>topic</em></span>: in the AMQP 0-10
mapping, a topic node defaults to the topic exchange, x-declare
- may be used to specify other exchange types</p></li><li class="listitem"><p><span class="emphasis"><em>queue</em></span>: this is the default node-type</p></li></ul></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.id381307" href="#id381307" class="para">2</a>] </sup>In the programs we have just seen, we used
+ may be used to specify other exchange types</p></li><li class="listitem"><p><span class="emphasis"><em>queue</em></span>: this is the default node-type</p></li></ul></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a id="ftn.id578768" href="#id578768" class="para">2</a>] </sup>In the programs we have just seen, we used
<code class="literal">amq.topic</code> 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.</p></div><div class="footnote"><p><sup>[<a id="ftn.id381334" href="#id381334" class="para">3</a>] </sup>The terms <span class="emphasis"><em>queue</em></span> and
+ exists on an AMQP 0-10 messaging broker.</p></div><div class="footnote"><p><sup>[<a id="ftn.id578795" href="#id578795" class="para">3</a>] </sup>The terms <span class="emphasis"><em>queue</em></span> and
<span class="emphasis"><em>topic</em></span> 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 @@
called a <span class="emphasis"><em>topic exchange</em></span>. When the term
<span class="emphasis"><em>topic</em></span> occurs alone, it refers to a
Messaging API topic, not the topic
- exchange.</p></div><div class="footnote"><p><sup>[<a id="ftn.id381355" href="#id381355" class="para">4</a>] </sup>There are exceptions to this rule; for instance,
+ exchange.</p></div><div class="footnote"><p><sup>[<a id="ftn.id578816" href="#id578816" class="para">4</a>] </sup>There are exceptions to this rule; for instance,
a receiver can use <code class="literal">browse</code> mode, which leaves
messages on the queue for other receivers to
- read.</p></div><div class="footnote"><p><sup>[<a id="ftn.id381368" href="#id381368" class="para">5</a>] </sup>The AMQP 0-10 implementation is the only one
- that currently exists.</p></div><div class="footnote"><p><sup>[<a id="ftn.id381374" href="#id381374" class="para">6</a>] </sup>In AMQP 0-10, messages are sent to
+ read.</p></div><div class="footnote"><p><sup>[<a id="ftn.id578829" href="#id578829" class="para">5</a>] </sup>The AMQP 0-10 implementation is the only one
+ that currently exists.</p></div><div class="footnote"><p><sup>[<a id="ftn.id578835" href="#id578835" class="para">6</a>] </sup>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 @@
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.</p></div><div class="footnote"><p><sup>[<a id="ftn.id381404" href="#id381404" class="para">7</a>] </sup>Currently, the C++, Python, and .NET C#
+ the topic.</p></div><div class="footnote"><p><sup>[<a id="ftn.id578865" href="#id578865" class="para">7</a>] </sup>Currently, the C++, Python, and .NET C#
implementations of <span class="command"><strong>drain</strong></span> and
<span class="command"><strong>spout</strong></span> have slightly different
options. This tutorial uses the C++ implementation. The
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org