qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From acon...@apache.org
Subject svn commit: r1309985 [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-...
Date Thu, 05 Apr 2012 18:19:03 GMT
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=1309985&r1=1309984&r2=1309985&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 18:19:00 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#id361262">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#id406630">2.4.1. Address Strings</a></span></dt><dt><span class="section"><a href="section-addresses.html#id406673">2.4.2. Subjects</a></span></dt><dt><span class="section"><a
  href="section-addresses.html#id407011">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#id409703">2.15.1. Logging in C++</a></span></dt><dt><span class="section"><a href="ch02s15.html#id409744">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#id410332">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#id410687">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#id411866">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="QpidWCF.html#id41
 2824">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#id413214">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#id413748">5.3.1. .NET Binding for the C++ M
 essaging API Class: Address</a></span></dt><dt><span class="section"><a href="ch05s03.html#id414338">5.3.2. .NET Binding for the C++ Messaging API Class: Connection</a></span></dt><dt><span class="section"><a href="ch05s03.html#id414964">5.3.3. .NET Binding for the C++ Messaging API Class: Duration</a></span></dt><dt><span class="section"><a href="ch05s03.html#id415375">5.3.4. .NET Binding for the C++ Messaging API Class: FailoverUpdates</a></span></dt><dt><span class="section"><a href="ch05s03.html#id415551">5.3.5. .NET Binding for the C++ Messaging API Class: Message</a></span></dt><dt><span class="section"><a href="ch05s03.html#id416703">5.3.6. .NET Binding for the C++ Messaging API Class: Receiver</a></span></dt><dt><span class="section"><a href="ch05s03.html#id417332">5.3.7. .NET Binding for the C++ Messaging API Class: Sender</a></span></dt><dt><span class="section"><a href="ch05s03.html#id417803">5.3.8. .NET Binding for the C++ Messaging API Class: Session</a></span><
 /dt><dt><span class="section"><a href="ch05s03.html#id418739">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#id407487">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#id408393">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#id410696">JNDI Properties supported by Apache Qpid</a></dt><dt>3.2. <a href="QpidJNDI.html#id410824">Connection URL Properties</a></dt><dt>3.3. <a href="QpidJNDI.html#id411080">Broker List Options</a></dt><dt>3.4. <a href="ch03s03.html#id411400">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#id411872">Config Options For Connection Behaviour</a></dt><dt>3.7. <a href="ch03s06.html#id411968">Config Options For Session Behaviour</a></dt><dt>3.8. <a href="ch03s06.html#id412055">Config Options For Consumer Behaviour</a></dt><dt>3.9. <a href="ch03s06.html#id412174">Config Options For Producer Behaviour</a></dt><dt>3.10. <a href="ch03s06.html#id412229">Config Options For Threading</a></dt><dt>3.
 11. <a href="ch03s06.html#id412304">Config Options For I/O</a></dt><dt>3.12. <a href="ch03s06.html#id412405">Config Options For Security</a></dt><dt>3.13. <a href="ch03s06.html#id412516">Config Options For Security - Standard JVM properties needed when using GSSAPI as the SASL mechanism.</a></dt><dt>3.14. <a href="ch03s06.html#id412602">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#id412694">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#id412908">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#id361272">"Hello world!" in C++</a></dt><dt>2.2. <a href="ch02s02.html#id360513">"Hello world!" in Python</a></dt><dt>2.3. <a href="c
 h02s03.html#id406110">"Hello world!" in .NET C#</a></dt><dt>2.4. <a href="section-addresses.html#id406421">Queues</a></dt><dt>2.5. <a href="section-addresses.html#id406496">Topics</a></dt><dt>2.6. <a href="section-addresses.html#id406706">Using subjects</a></dt><dt>2.7. <a href="section-addresses.html#id406879">Subjects with multi-word keys</a></dt><dt>2.8. <a href="section-addresses.html#id407126">Assertions on Nodes</a></dt><dt>2.9. <a href="section-addresses.html#id407205">Creating a Queue Automatically</a></dt><dt>2.10. <a href="section-addresses.html#id407274">Browsing a Queue</a></dt><dt>2.11. <a href="section-addresses.html#id407385">Using the XML Exchange</a></dt><dt>2.12. <a href="ch02s08.html#id408185">Receiving Messages from Multiple Sources</a></dt><dt>2.13. <a href="ch02s09.html#id408255">Transactions</a></dt><dt>2.14. <a href="connection-options.html#id408300">Specifying Connection Options in C++, Python, and .NET</a></dt><dt>2.15. <a href="section-Maps.html#id
 408863">Sending Qpid Maps and Lists in Python</a></dt><dt>2.16. <a href="section-Maps.html#id409013">Sending Qpid Maps and Lists in C++</a></dt><dt>2.17. <a href="section-Maps.html#id409206">Sending Qpid Maps and Lists in .NET C#</a></dt><dt>2.18. <a href="ch02s12.html#id409485">Request / Response Applications in C++</a></dt><dt>2.19. <a href="ch02s14.html#id409649">Tracking cluster membership</a></dt><dt>2.20. <a href="section-amqp0-10-mapping.html#id410274">Accessing the AMQP 0-10 Message Timestamp in Python</a></dt><dt>2.21. <a href="section-amqp0-10-mapping.html#id410294">Accessing the AMQP 0-10 Message Timestamp in C++</a></dt><dt>2.22. <a href="Message-Groups-Guide.html#id409245">Message Group Queue Creation - Python</a></dt><dt>2.23. <a href="Message-Groups-Guide.html#id409260">Message Group Queue Creation - C++</a></dt><dt>2.24. <a href="Message-Groups-Guide.html#id409276">Message Group Queue Creation - Java</a></dt><dt>2.25. <a href="Message-Groups-Guide.html#id3597
 39">Sending Grouped Messages - Python</a></dt><dt>2.26. <a href="Message-Groups-Guide.html#id359755">Sending Grouped Messages - C++</a></dt><dt>2.27. <a href="Message-Groups-Guide.html#id359772">Sending Grouped Messages - Java</a></dt><dt>3.1. <a href="QpidJMS.html#id410350">"Hello world!" in Java</a></dt><dt>3.2. <a href="QpidJMS.html#id410592">JNDI Properties File for "Hello world!" example</a></dt><dt>3.3. <a href="QpidJNDI.html#id410668">JNDI Properties File</a></dt><dt>3.4. <a href="QpidJNDI.html#id411036">Broker Lists</a></dt><dt>3.5. <a href="section-JMS-MapMessage.html#id411566">Sending a Java JMS MapMessage</a></dt><dt>3.6. <a href="section-JMS-Logging.html#id411762">log4j Logging Properties</a></dt><dt>4.1. <a href="QpidWCF.html#id412842">Traditional service model "Hello world!" example</a></dt><dt>4.2. <a href="QpidWCF.html#id412869">Binary  "Hello world!" example using the channel model</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summa
 ry="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#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>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/prefetch.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/prefetch.html?rev=1309985&r1=1309984&r2=1309985&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/prefetch.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/prefetch.html Thu Apr  5 18:19:00 2012
@@ -1,9 +1,9 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.6. Receiver Capacity (Prefetch)</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="replay.html" title="2.5. Sender Capacity and Replay"><link rel="next" href="acknowledgements.html" title="2.7. Acknowledging Received Messages"></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.6. Receiver Capacity (Prefetch)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="replay.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="acknowledgements.html">Next</a></td></tr></table><hr></div><div class="section" title="2.6. Receiver Capacity (Prefetch)"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="prefetch"></a>2.6. Receiver Capacity (Prefetch)</h2></div></div></div><p>By default, a receiver requests the next message from the
-    server in response to each fetch call, resulting in messages being
-    sent to the receiver one at a time. As in the case of sending, it
-    is often desirable to avoid this roundtrip for each message. This
-    can be achieved by allowing the receiver
-    to <em class="firstterm">prefetch</em> messages in anticipation of
-    fetch calls being made. The receiver needs to be able to store
-    these prefetched messages, the number it can hold is controlled by
-    the receivers capacity.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="replay.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="acknowledgements.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.5. Sender Capacity and Replay </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.7. Acknowledging Received Messages</td></tr></table></div></body></html>
+      server in response to each fetch call, resulting in messages being
+      sent to the receiver one at a time. As in the case of sending, it
+      is often desirable to avoid this roundtrip for each message. This
+      can be achieved by allowing the receiver
+      to <em class="firstterm">prefetch</em> messages in anticipation of
+      fetch calls being made. The receiver needs to be able to store
+      these prefetched messages, the number it can hold is controlled by
+      the receivers capacity.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="replay.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="acknowledgements.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.5. Sender Capacity and Replay </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.7. Acknowledging Received Messages</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/replay.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/replay.html?rev=1309985&r1=1309984&r2=1309985&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/replay.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/replay.html Thu Apr  5 18:19:00 2012
@@ -1,25 +1,25 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.5. Sender Capacity and Replay</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="section-addresses.html" title="2.4. Addresses"><link rel="next" href="prefetch.html" title="2.6. Receiver Capacity (Prefetch)"></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.5. Sender Capacity and Replay</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="section-addresses.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Using the Qpid Messaging API</th><td wid
 th="20%" align="right"> <a accesskey="n" href="prefetch.html">Next</a></td></tr></table><hr></div><div class="section" title="2.5. Sender Capacity and Replay"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="replay"></a>2.5. Sender Capacity and Replay</h2></div></div></div><p>The send method of a sender has an optional second parameter
-    that controls whether the send call is synchronous or not. A
-    synchronous send call will block until the broker has confirmed
-    receipt of the message. An asynchronous send call will return
-    before the broker confirms receipt of the message, allowing for
-    example further send calls to be made without waiting for a
-    roundtrip to the broker for each message. This is desirable where
-    increased throughput is important.</p><p>The sender maintains a list of sent messages whose receipt
-    has yet to be confirmed by the broker. The maximum number of such
-    messages that it will hold is defined by the capacity of the
-    sender, which can be set by the application. If an application
-    tries to send with a sender whose capacity is already fully used
-    up, the send call will block waiting for capacity regardless of
-    the value of the sync flag.</p><p>The sender can be queried for the available space (i.e. the
-    unused capacity), and for the current count of unsettled messages
-    (i.e. those held in the replay list pending confirmation by the
-    server). When the unsettled count is zero, all messages on that
-    sender have been successfully sent.</p><p>If the connection fails and is transparently reconnected
-    (see <a class="xref" href="connection-options.html" title="2.10. Connection Options">Section 2.10, “Connection Options”</a> for details on how to control
-    this feature), the unsettled messages for each sender over that
-    connection will be re-transmitted. This provides a transparent
-    level of reliability. This feature can be controlled through the
-    link's reliability as defined in the address (see
-    <a class="xref" href="section-addresses.html#table-link-properties" title="Table 2.3. Link Properties">Table 2.3, “Link Properties”</a>). At present only
-    at-least-once guarantees are offered. </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="section-addresses.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="prefetch.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.4. Addresses </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.6. Receiver Capacity (Prefetch)</td></tr></table></div></body></html>
+      that controls whether the send call is synchronous or not. A
+      synchronous send call will block until the broker has confirmed
+      receipt of the message. An asynchronous send call will return
+      before the broker confirms receipt of the message, allowing for
+      example further send calls to be made without waiting for a
+      roundtrip to the broker for each message. This is desirable where
+      increased throughput is important.</p><p>The sender maintains a list of sent messages whose receipt
+      has yet to be confirmed by the broker. The maximum number of such
+      messages that it will hold is defined by the capacity of the
+      sender, which can be set by the application. If an application
+      tries to send with a sender whose capacity is already fully used
+      up, the send call will block waiting for capacity regardless of
+      the value of the sync flag.</p><p>The sender can be queried for the available space (i.e. the
+      unused capacity), and for the current count of unsettled messages
+      (i.e. those held in the replay list pending confirmation by the
+      server). When the unsettled count is zero, all messages on that
+      sender have been successfully sent.</p><p>If the connection fails and is transparently reconnected
+      (see <a class="xref" href="connection-options.html" title="2.10. Connection Options">Section 2.10, “Connection Options”</a> for details on how to control
+      this feature), the unsettled messages for each sender over that
+      connection will be re-transmitted. This provides a transparent
+      level of reliability. This feature can be controlled through the
+      link's reliability as defined in the address (see
+      <a class="xref" href="section-addresses.html#table-link-properties" title="Table 2.3. Link Properties">Table 2.3, “Link Properties”</a>). At present only
+      at-least-once guarantees are offered. </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="section-addresses.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="prefetch.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.4. Addresses </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.6. Receiver Capacity (Prefetch)</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=1309985&r1=1309984&r2=1309985&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 18:19:00 2012
@@ -1,9 +1,9 @@
-<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="id411762"></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
+<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">
+	log4j.logger.org.apache.qpid=WARN, console
+	log4j.additivity.org.apache.qpid=false
 
-log4j.appender.console=org.apache.log4j.ConsoleAppender
-log4j.appender.console.Threshold=all
-log4j.appender.console.layout=org.apache.log4j.PatternLayout
-log4j.appender.console.layout.ConversionPattern=%t %d %p [%c{4}] %m%n
-</pre></div></div><br class="example-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="section-JMS-MapMessage.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="ch03s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.4. JMS MapMessage Types </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.6. Configuring the JMS Client</td></tr></table></div></body></html>
+	log4j.appender.console=org.apache.log4j.ConsoleAppender
+	log4j.appender.console.Threshold=all
+	log4j.appender.console.layout=org.apache.log4j.PatternLayout
+	log4j.appender.console.layout.ConversionPattern=%t %d %p [%c{4}] %m%n
+	</pre></div></div><br class="example-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="section-JMS-MapMessage.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="ch03s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.4. JMS MapMessage Types </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.6. Configuring the JMS Client</td></tr></table></div></body></html>

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=1309985&r1=1309984&r2=1309985&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 18:19:00 2012
@@ -1,48 +1,48 @@
-<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="id411566"></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;
-import java.util.Map;
-
-import javax.jms.Connection;
-import javax.jms.Destination;
-import javax.jms.MapMessage;
-import javax.jms.MessageProducer;
-import javax.jms.Session;
-
-import java.util.Arrays;
-
-// !!! SNIP !!!
-
-MessageProducer producer = session.createProducer(queue);
-
-MapMessage m = session.createMapMessage();
-m.setIntProperty("Id", 987654321);
-m.setStringProperty("name", "Widget");
-m.setDoubleProperty("price", 0.99);
-
-List&lt;String&gt; colors = new ArrayList&lt;String&gt;();
-colors.add("red");
-colors.add("green");
-colors.add("white");
-m.setObject("colours", colors);
-
-Map&lt;String,Double&gt; dimensions = new HashMap&lt;String,Double&gt;();
-dimensions.put("length",10.2);
-dimensions.put("width",5.1);
-dimensions.put("depth",2.0);
-m.setObject("dimensions",dimensions);
-
-List&lt;List&lt;Integer&gt;&gt; parts = new ArrayList&lt;List&lt;Integer&gt;&gt;();
-parts.add(Arrays.asList(new Integer[] {1,2,5}));
-parts.add(Arrays.asList(new Integer[] {8,2,5}));
-m.setObject("parts", parts);
-
-Map&lt;String,Object&gt; specs = new HashMap&lt;String,Object&gt;();
-specs.put("colours", colors);
-specs.put("dimensions", dimensions);
-specs.put("parts", parts);
-m.setObject("specs",specs);
+<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">
+	import java.util.ArrayList;
+	import java.util.HashMap;
+	import java.util.List;
+	import java.util.Map;
+
+	import javax.jms.Connection;
+	import javax.jms.Destination;
+	import javax.jms.MapMessage;
+	import javax.jms.MessageProducer;
+	import javax.jms.Session;
+
+	import java.util.Arrays;
+
+	// !!! SNIP !!!
+
+	MessageProducer producer = session.createProducer(queue);
+
+	MapMessage m = session.createMapMessage();
+	m.setIntProperty("Id", 987654321);
+	m.setStringProperty("name", "Widget");
+	m.setDoubleProperty("price", 0.99);
+
+	List&lt;String&gt; colors = new ArrayList&lt;String&gt;();
+	colors.add("red");
+	colors.add("green");
+	colors.add("white");
+	m.setObject("colours", colors);
+
+	Map&lt;String,Double&gt; dimensions = new HashMap&lt;String,Double&gt;();
+	dimensions.put("length",10.2);
+	dimensions.put("width",5.1);
+	dimensions.put("depth",2.0);
+	m.setObject("dimensions",dimensions);
+
+	List&lt;List&lt;Integer&gt;&gt; parts = new ArrayList&lt;List&lt;Integer&gt;&gt;();
+	parts.add(Arrays.asList(new Integer[] {1,2,5}));
+	parts.add(Arrays.asList(new Integer[] {8,2,5}));
+	m.setObject("parts", parts);
+
+	Map&lt;String,Object&gt; specs = new HashMap&lt;String,Object&gt;();
+	specs.put("colours", colors);
+	specs.put("dimensions", dimensions);
+	specs.put("parts", parts);
+	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="id411697" href="#ftn.id411697" 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.id411697" href="#id411697" 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 Propertie
 s </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>
+	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>

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=1309985&r1=1309984&r2=1309985&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 18:19:00 2012
@@ -2,156 +2,156 @@
       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="id408712" href="#ftn.id408712" class="footnote">9</a>]</sup>
+      <sup>[<a name="id383789" href="#ftn.id383789" class="footnote">9</a>]</sup>
 
-			<sup>[<a name="id408717" href="#ftn.id408717" 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&lt;string, object&gt;</code></td><td><code class="classname">Collection&lt;object&gt;</code></td></tr></tbody></table></div></div><br class="table-break"><p>
-			In all languages, messages are encoded using AMQP's portable datatypes.
+      <sup>[<a name="id383794" href="#ftn.id383794" 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&lt;string, object&gt;</code></td><td><code class="classname">Collection&lt;object&gt;</code></td></tr></tbody></table></div></div><br class="table-break"><p>
+	In all languages, messages are encoded using AMQP's portable datatypes.
       </p><div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>Because of the differences in type systems among
-      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="id408863"></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 !!!
-
-content = {'Id' : 987654321, 'name' : 'Widget', 'percent' : 0.99}
-content['colours'] = ['red', 'green', 'white']
-content['dimensions'] = {'length' : 10.2, 'width' : 5.1,'depth' : 2.0};
-content['parts'] = [ [1,2,5], [8,2,5] ]
-content['specs'] = {'colors' : content['colours'],
-                    'dimensions' : content['dimensions'],
-                    'parts' : content['parts'] }
-message = Message(content=content)
-sender.send(message)
-       </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent in a Python map message,
- and the corresponding datatypes that will be received by clients in Java or C++.</p><div class="table"><a name="table-Python-Maps"></a><p class="title"><b>Table 2.6. Python Datatypes in Maps</b></p><div class="table-contents"><table summary="Python Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Python Datatype</th><th>→ C++</th><th>→ Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>int</td><td>int64</td><td>long</td></tr><tr><td>long</td><td>int64</td><td>long</td></tr><tr><td>float</td><td>double</td><td>double</td></tr><tr><td>unicode</td><td>string</td><td>java.lang.String</td></tr><tr><td>uuid</td><td>qpid::types::Uuid</td><td>java.util.UUID</td></tr><tr><td>dict</td><td>Variant::Map</td><td>java.util.Map</td></tr><tr><td>list</td><td>Variant::List</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.2. Qpid Ma
 ps and Lists in C++"><div class="titlepage"><div><div><h3 class="title"><a name="section-cpp-Maps"></a>2.11.2. Qpid Maps and Lists in C++</h3></div></div></div><p>In C++, Qpid defines the the
+	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">
+	  from qpid.messaging import *
+	  # !!! SNIP !!!
+
+	  content = {'Id' : 987654321, 'name' : 'Widget', 'percent' : 0.99}
+	  content['colours'] = ['red', 'green', 'white']
+	  content['dimensions'] = {'length' : 10.2, 'width' : 5.1,'depth' : 2.0};
+	  content['parts'] = [ [1,2,5], [8,2,5] ]
+	  content['specs'] = {'colors' : content['colours'],
+	  'dimensions' : content['dimensions'],
+	  'parts' : content['parts'] }
+	  message = Message(content=content)
+	  sender.send(message)
+	     </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent in a Python map message,
+	and the corresponding datatypes that will be received by clients in Java or C++.</p><div class="table"><a name="table-Python-Maps"></a><p class="title"><b>Table 2.6. Python Datatypes in Maps</b></p><div class="table-contents"><table summary="Python Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Python Datatype</th><th>→ C++</th><th>→ Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>int</td><td>int64</td><td>long</td></tr><tr><td>long</td><td>int64</td><td>long</td></tr><tr><td>float</td><td>double</td><td>double</td></tr><tr><td>unicode</td><td>string</td><td>java.lang.String</td></tr><tr><td>uuid</td><td>qpid::types::Uuid</td><td>java.util.UUID</td></tr><tr><td>dict</td><td>Variant::Map</td><td>java.util.Map</td></tr><tr><td>list</td><td>Variant::List</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.2. Qpid Ma
 ps and Lists in C++"><div class="titlepage"><div><div><h3 class="title"><a name="section-cpp-Maps"></a>2.11.2. Qpid Maps and Lists in C++</h3></div></div></div><p>In C++, Qpid defines the the
 	<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="id409013"></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;
+	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">
+	  using namespace qpid::types;
 
-// !!! SNIP !!!
+	  // !!! SNIP !!!
 
-Message message;
-Variant::Map content;
-content["id"] = 987654321;
-content["name"] = "Widget";
-content["percent"] = 0.99;
-Variant::List colours;
-colours.push_back(Variant("red"));
-colours.push_back(Variant("green"));
-colours.push_back(Variant("white"));
-content["colours"] = colours;
-
-Variant::Map dimensions;
-dimensions["length"] = 10.2;
-dimensions["width"] = 5.1;
-dimensions["depth"] = 2.0;
-content["dimensions"]= dimensions;
-
-Variant::List part1;
-part1.push_back(Variant(1));
-part1.push_back(Variant(2));
-part1.push_back(Variant(5));
-
-Variant::List part2;
-part2.push_back(Variant(8));
-part2.push_back(Variant(2));
-part2.push_back(Variant(5));
-
-Variant::List parts;
-parts.push_back(part1);
-parts.push_back(part2);
-content["parts"]= parts;
-
-Variant::Map specs;
-specs["colours"] = colours;
-specs["dimensions"] = dimensions;
-specs["parts"] = parts;
-content["specs"] = specs;
-
-encode(content, message);
-sender.send(message, true);
-     </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent
+	  Message message;
+	  Variant::Map content;
+	  content["id"] = 987654321;
+	  content["name"] = "Widget";
+	  content["percent"] = 0.99;
+	  Variant::List colours;
+	  colours.push_back(Variant("red"));
+	  colours.push_back(Variant("green"));
+	  colours.push_back(Variant("white"));
+	  content["colours"] = colours;
+
+	  Variant::Map dimensions;
+	  dimensions["length"] = 10.2;
+	  dimensions["width"] = 5.1;
+	  dimensions["depth"] = 2.0;
+	  content["dimensions"]= dimensions;
+
+	  Variant::List part1;
+	  part1.push_back(Variant(1));
+	  part1.push_back(Variant(2));
+	  part1.push_back(Variant(5));
+
+	  Variant::List part2;
+	  part2.push_back(Variant(8));
+	  part2.push_back(Variant(2));
+	  part2.push_back(Variant(5));
+
+	  Variant::List parts;
+	  parts.push_back(part1);
+	  parts.push_back(part2);
+	  content["parts"]= parts;
+
+	  Variant::Map specs;
+	  specs["colours"] = colours;
+	  specs["dimensions"] = dimensions;
+	  specs["parts"] = parts;
+	  content["specs"] = specs;
+
+	  encode(content, message);
+	  sender.send(message, true);
+	       </pre></div></div><br class="example-break"><p>The following table shows the datatypes that can be sent
 	in a C++ map message, and the corresponding datatypes that
 	will be received by clients in Java and Python.</p><div class="table"><a name="table-cpp-Maps"></a><p class="title"><b>Table 2.7. C++ Datatypes in Maps</b></p><div class="table-contents"><table summary="C++ Datatypes in Maps" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>C++ Datatype</th><th>→ Python</th><th>→ Java</th></tr></thead><tbody><tr><td>bool</td><td>bool</td><td>boolean</td></tr><tr><td>uint16</td><td>int | long</td><td>short</td></tr><tr><td>uint32</td><td>int | long</td><td>int</td></tr><tr><td>uint64</td><td>int | long</td><td>long</td></tr><tr><td>int16</td><td>int | long</td><td>short</td></tr><tr><td>int32</td><td>int | long</td><td>int</td></tr><tr><td>int64</td><td>int | long</td><td>long</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>string</td><td>unicode</td><td>java.lang.String</td></tr><tr><td>qpid::types::Uuid</td><td>uuid</td><td>java.util.UUID<
 /td></tr><tr><td>Variant::Map</td><td>dict</td><td>java.util.Map</td></tr><tr><td>Variant::List</td><td>list</td><td>java.util.List</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.11.3. Qpid Maps and Lists in .NET"><div class="titlepage"><div><div><h3 class="title"><a name="section-dotnet-Maps"></a>2.11.3. Qpid Maps and Lists in .NET</h3></div></div></div><p>
 	  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="id409206"></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;
+	</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">
+	  using System;
+	  using Org.Apache.Qpid.Messaging;
 
-// !!! SNIP !!!
+	  // !!! SNIP !!!
 
-Dictionary&lt;string, object&gt; content = new Dictionary&lt;string, object&gt;();
-Dictionary&lt;string, object&gt; subMap = new Dictionary&lt;string, object&gt;();
-Collection&lt;object&gt; colors = new Collection&lt;object&gt;();
+	  Dictionary&lt;string, object&gt; content = new Dictionary&lt;string, object&gt;();
+	  Dictionary&lt;string, object&gt; subMap = new Dictionary&lt;string, object&gt;();
+	  Collection&lt;object&gt; colors = new Collection&lt;object&gt;();
 
-// add simple types
-content["id"] = 987654321;
-content["name"] = "Widget";
-content["percent"] = 0.99;
+	  // add simple types
+	  content["id"] = 987654321;
+	  content["name"] = "Widget";
+	  content["percent"] = 0.99;
 
-// add nested amqp/map
-subMap["name"] = "Smith";
-subMap["number"] = 354;
-content["nestedMap"] = subMap;
+	  // add nested amqp/map
+	  subMap["name"] = "Smith";
+	  subMap["number"] = 354;
+	  content["nestedMap"] = subMap;
 
-// add an amqp/list
-colors.Add("red");
-colors.Add("green");
-colors.Add("white");
-content["colorsList"] = colors;
+	  // add an amqp/list
+	  colors.Add("red");
+	  colors.Add("green");
+	  colors.Add("white");
+	  content["colorsList"] = colors;
 
-// add one of each supported amqp data type
-bool mybool = true;
-content["mybool"] = mybool;
+	  // add one of each supported amqp data type
+	  bool mybool = true;
+	  content["mybool"] = mybool;
 
-byte mybyte = 4;
-content["mybyte"] = mybyte;
+	  byte mybyte = 4;
+	  content["mybyte"] = mybyte;
 
-UInt16 myUInt16 = 5;
-content["myUInt16"] = myUInt16;
+	  UInt16 myUInt16 = 5;
+	  content["myUInt16"] = myUInt16;
 
-UInt32 myUInt32 = 6;
-content["myUInt32"] = myUInt32;
+	  UInt32 myUInt32 = 6;
+	  content["myUInt32"] = myUInt32;
 
-UInt64 myUInt64 = 7;
-content["myUInt64"] = myUInt64;
+	  UInt64 myUInt64 = 7;
+	  content["myUInt64"] = myUInt64;
 
-char mychar = 'h';
-content["mychar"] = mychar;
+	  char mychar = 'h';
+	  content["mychar"] = mychar;
 
-Int16 myInt16 = 9;
-content["myInt16"] = myInt16;
+	  Int16 myInt16 = 9;
+	  content["myInt16"] = myInt16;
 
-Int32 myInt32 = 10;
-content["myInt32"] = myInt32;
+	  Int32 myInt32 = 10;
+	  content["myInt32"] = myInt32;
 
-Int64 myInt64 = 11;
-content["myInt64"] = myInt64;
+	  Int64 myInt64 = 11;
+	  content["myInt64"] = myInt64;
 
-Single mySingle = (Single)12.12;
-content["mySingle"] = mySingle;
+	  Single mySingle = (Single)12.12;
+	  content["mySingle"] = mySingle;
 
-Double myDouble = 13.13;
-content["myDouble"] = myDouble;
+	  Double myDouble = 13.13;
+	  content["myDouble"] = myDouble;
 
-Guid myGuid = new Guid("000102030405060708090a0b0c0d0e0f");
-content["myGuid"] = myGuid;
+	  Guid myGuid = new Guid("000102030405060708090a0b0c0d0e0f");
+	  content["myGuid"] = myGuid;
 
-Message message = new Message(content);
-Send(message, true);
-     </pre></div></div><br class="example-break"><p>
+	  Message message = new Message(content);
+	  Send(message, true);
+	       </pre></div></div><br class="example-break"><p>
 	  The following table shows the mapping between datatypes in .NET and C++.
 	</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&lt;string, object&gt;
-          <sup>[<a href="section-Maps.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr><tr><td>Variant::List</td><td>Collection&lt;object&gt;
-          <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.id408712" href="#id408712" 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.id408717" href="#id408717" 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>
+	      <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&lt;string, object&gt;
+	      <sup>[<a href="section-Maps.html#ftn.callout-dotnet-string" class="footnoteref">a</a>]</sup></td></tr><tr><td>Variant::List</td><td>Collection&lt;object&gt;
+	      <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>
+	  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>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org


Mime
View raw message