qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jonat...@apache.org
Subject svn commit: r967163 [3/4] - in /qpid/site/docs/books/0.7/Programming-In-Apache-Qpid: html/ pdf/
Date Fri, 23 Jul 2010 16:48:12 GMT
Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03.html Fri Jul 23 16:48:11 2010
@@ -1,18 +1,14 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Using the Qpid JMS client</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="index.html" title="Programming in Apache Qpid"><link rel="prev" href="ch02s13.html" title="13. The AMQP 0-10 mapping"><link rel="next" href="ch03s02.html" title="2. Apache Qpid JNDI Properties for AMQP Messaging"></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">Chapter 3. Using the Qpid JMS client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s13.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch03s02.html">Next</a></td></tr></table><hr></div><div class
 ="chapter" title="Chapter 3. Using the Qpid JMS client"><div class="titlepage"><div><div><h2 class="title"><a name="QpidJMS"></a>Chapter 3. Using the Qpid JMS client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch03.html#id2788645">1. A Simple Messaging Program in Java JMS</a></span></dt><dt><span class="section"><a href="ch03s02.html">2. Apache Qpid JNDI Properties for AMQP Messaging</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#id2789002">2.1. JNDI Properties for Apache Qpid</a></span></dt><dt><span class="section"><a href="ch03s02.html#id2789111">2.2. Connection URLs</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s03.html">3. Java JMS Message Properties</a></span></dt><dt><span class="section"><a href="ch03s04.html">4. JMS MapMessage Types</a></span></dt><dt><span class="section"><a href="ch03s05.html">5. JMS Client Logging</a></span></dt></dl></div><div class="se
 ction" title="1. A Simple Messaging Program in Java JMS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2788645"></a>1. A Simple Messaging Program in Java JMS</h2></div></div></div><p>The following program shows how to use address strings and
-      JNDI for Qpid programs that use Java JMS.</p><p>The Qpid JMS client uses Qpid Messaging API <a class="xref" href="ch02s04.html" title="4. Addresses">Section 4, &#8220;Addresses&#8221;</a> to identify sources and
-      targets. This program uses a JNDI properties file that defines a
-      connection factory for the broker we are using, and the address
-      of the topic exchange node that we bind the sender and receiver
-      to. (The syntax of a ConnectionURL is given in <a class="xref" href="ch03s02.html" title="2. Apache Qpid JNDI Properties for AMQP Messaging">Section 2, &#8220;Apache Qpid JNDI Properties for AMQP Messaging&#8221;</a>.)</p><div class="example"><a name="id2788674"></a><p class="title"><b>Example 3.1. JNDI Properties File for "Hello world!" example</b></p><div class="example-contents"><pre class="programlisting">
-java.naming.factory.initial 
-  = org.apache.qpid.jndi.PropertiesFileInitialContextFactory
-
-# connectionfactory.[jndiname] = [ConnectionURL]
-connectionfactory.qpidConnectionfactory 
-  = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672'
-# destination.[jndiname] = [address_string]
-destination.topicExchange = amq.topic
-</pre></div></div><br class="example-break"><p>In the Java JMS code, we use create a JNDI context, use the context to find a connection factory and create and start a connection, create a session, and create a destination that corresponds to the topic exchange. Then we create a sender and a receiver, send a message with the sender, and receive it with the receiver. This code should be straightforward for anyone familiar with Java JMS.</p><div class="example"><a name="id2788689"></a><p class="title"><b>Example 3.2. "Hello world!" in Java</b></p><div class="example-contents"><pre lang="java" class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Using the Qpid JMS client</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="index.html" title="Programming in Apache Qpid"><link rel="prev" href="ch02s16.html" title="2.16. The AMQP 0-10 mapping"><link rel="next" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging"></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">Chapter 3. Using the Qpid JMS client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s16.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch03s02.html">Next</a></td></tr></table><hr></div><div c
 lass="chapter" title="Chapter 3. Using the Qpid JMS client"><div class="titlepage"><div><div><h2 class="title"><a name="QpidJMS"></a>Chapter 3. Using the Qpid JMS client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch03.html#id2588496">3.1. A Simple Messaging Program in Java JMS</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Apache Qpid JNDI Properties for AMQP Messaging</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#id2588909">3.2.1. JNDI Properties for Apache Qpid</a></span></dt><dt><span class="section"><a href="ch03s02.html#id2589017">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="ch03s04.html">3.4. JMS MapMessage Types</a></span></dt><dt><span class="section"><a href="ch03s05.html">3.5. JMS Client Logging</a></span></dt></dl></
 div><div class="section" title="3.1. A Simple Messaging Program in Java JMS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2588496"></a>3.1. A Simple Messaging Program in Java JMS</h2></div></div></div><p>The following program shows how to send and receive a
+      message using the Qpid JMS client. JMS programs typically use
+      JNDI to obtain connection factory and destination objects which
+      the application needs. In this way the configuration is kept
+      separate from the application code itself.</p><p>In this example, we create a JNDI context using a
+      properties file, use the context to lookup a connection factory,
+      create and start a connection, create a session, and lookup a
+      destination from the JNDI context. Then we create a producer and
+      a consumer, send a message with the producer and receive it with
+      the consumer. This code should be straightforward for anyone
+      familiar with Java JMS.</p><div class="example"><a name="id2588521"></a><p class="title"><b>Example 3.1. "Hello world!" in Java</b></p><div class="example-contents"><pre lang="java" class="programlisting">
 package org.apache.qpid.example.jmsexample.hello;
 
 import javax.jms.*;
@@ -61,4 +57,22 @@ public class Hello {
     }
   }
 }
-	</pre></div></div><br class="example-break"><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-properties"></a><a href="#hello-java-properties">(1)</a> </p></td><td valign="top" align="left"><p>Loads the JNDI properties file, which specifies connection properties, queues, topics, and addressing options. See <a class="xref" href="ch03s02.html" title="2. Apache Qpid JNDI Properties for AMQP Messaging">Section 2, &#8220;Apache Qpid JNDI Properties for AMQP Messaging&#8221;</a> for details.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-context"></a><a href="#hello-java-context">(2)</a> </p></td><td valign="top" align="left"><p>Creates the JNDI initial context.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection-factory"></a><a href="#hello-java-connection-factory">(3)</a> </p></td><td valign="top" align="left"><p>C
 reates a JMS connection factory for Qpid.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection"></a><a href="#hello-java-connection">(4)</a> </p></td><td valign="top" align="left"><p>Creates a JMS connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-start"></a><a href="#hello-java-start">(5)</a> </p></td><td valign="top" align="left"><p>Activates the connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-session"></a><a href="#hello-java-session">(6)</a> </p></td><td valign="top" align="left"><p>Creates a session. This session is not transactional (transactions='false'), and messages are automatically acknowledged.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-destination"></a><a href="#hello-java-destination">(7)</a> </p></td><td valign="top" align="left"><p>Creates a destination for the topic exchange, so senders an
 d receivers can use it.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-producer"></a><a href="#hello-java-producer">(8)</a> </p></td><td valign="top" align="left"><p>Creates a producer that sends messages to the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-consumer"></a><a href="#hello-java-consumer">(9)</a> </p></td><td valign="top" align="left"><p>Creates a consumer that reads messages from the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-receive"></a><a href="#hello-java-receive">(10)</a> </p></td><td valign="top" align="left"><p>Reads the next available message.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-close"></a><a href="#hello-java-close">(11)</a> </p></td><td valign="top" align="left"><p>Closes the connection, all sessions managed by the connection, and all senders and receivers manage
 d by each session.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-jndi-close"></a><a href="#hello-java-jndi-close">(12)</a> </p></td><td valign="top" align="left"><p>Closes the JNDI context.</p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s13.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch03s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13. The AMQP 0-10 mapping </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2. Apache Qpid JNDI Properties for AMQP Messaging</td></tr></table></div></body></html>
+	</pre></div></div><br class="example-break"><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-properties"></a><a href="#hello-java-properties">(1)</a> </p></td><td valign="top" align="left"><p>Loads the JNDI properties file, which specifies connection properties, queues, topics, and addressing options. See <a class="xref" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging">Section 3.2, &#8220;Apache Qpid JNDI Properties for AMQP Messaging&#8221;</a> for details.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-context"></a><a href="#hello-java-context">(2)</a> </p></td><td valign="top" align="left"><p>Creates the JNDI initial context.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection-factory"></a><a href="#hello-java-connection-factory">(3)</a> </p></td><td valign="top" align="left">
 <p>Creates a JMS connection factory for Qpid.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-connection"></a><a href="#hello-java-connection">(4)</a> </p></td><td valign="top" align="left"><p>Creates a JMS connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-start"></a><a href="#hello-java-start">(5)</a> </p></td><td valign="top" align="left"><p>Activates the connection.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-session"></a><a href="#hello-java-session">(6)</a> </p></td><td valign="top" align="left"><p>Creates a session. This session is not transactional (transactions='false'), and messages are automatically acknowledged.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-destination"></a><a href="#hello-java-destination">(7)</a> </p></td><td valign="top" align="left"><p>Creates a destination for the topic exchange, so sender
 s and receivers can use it.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-producer"></a><a href="#hello-java-producer">(8)</a> </p></td><td valign="top" align="left"><p>Creates a producer that sends messages to the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-consumer"></a><a href="#hello-java-consumer">(9)</a> </p></td><td valign="top" align="left"><p>Creates a consumer that reads messages from the topic exchange.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-receive"></a><a href="#hello-java-receive">(10)</a> </p></td><td valign="top" align="left"><p>Reads the next available message.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-close"></a><a href="#hello-java-close">(11)</a> </p></td><td valign="top" align="left"><p>Closes the connection, all sessions managed by the connection, and all senders and receivers ma
 naged by each session.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-java-jndi-close"></a><a href="#hello-java-jndi-close">(12)</a> </p></td><td valign="top" align="left"><p>Closes the JNDI context.</p></td></tr></table></div><p>The contents of the hello.properties file are shown below.</p><div class="example"><a name="id2588787"></a><p class="title"><b>Example 3.2. JNDI Properties File for "Hello world!" example</b></p><div class="example-contents"><pre class="programlisting">
+java.naming.factory.initial 
+  = org.apache.qpid.jndi.PropertiesFileInitialContextFactory
+
+# connectionfactory.[jndiname] = [ConnectionURL]
+connectionfactory.qpidConnectionfactory 
+  = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672' <a class="co" name="hello-properties-connectionfactory" href="ch03.html#callout-hello-properties-connectionfactory">(1)</a>
+# destination.[jndiname] = [address_string]
+destination.topicExchange = amq.topic <a class="co" name="hello-properties-destination" href="ch03.html#callout-hello-properties-destination">(2)</a>
+     </pre></div></div><br class="example-break"><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><p><a name="callout-hello-properties-connectionfactory"></a><a href="#hello-properties-connectionfactory">(1)</a> </p></td><td valign="top" align="left"><p>Defines a connection factory from which connections
+	  can be created. The syntax of a ConnectionURL is given in
+	  <a class="xref" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging">Section 3.2, &#8220;Apache Qpid JNDI Properties for AMQP Messaging&#8221;</a>.</p></td></tr><tr><td width="5%" valign="top" align="left"><p><a name="callout-hello-properties-destination"></a><a href="#hello-properties-destination">(2)</a> </p></td><td valign="top" align="left"><p>Defines a destination for which MessageProducers
+	  and/or MessageConsumers can be created to send and receive
+	  messages. The value for the destination in the properties
+	  file is an address string as described in
+	  <a class="xref" href="ch02s04.html" title="2.4. Addresses">Section 2.4, &#8220;Addresses&#8221;</a>. In the JMS
+	  implementation MessageProducers are analogous to senders in
+	  the Qpid Message API, and MessageConsumers are analogous to
+	  receivers.</p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s16.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch03s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.16. The AMQP 0-10 mapping </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.2. Apache Qpid JNDI Properties for AMQP Messaging</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s02.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s02.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s02.html Fri Jul 23 16:48:11 2010
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2. Apache Qpid JNDI Properties for AMQP Messaging</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="next" href="ch03s03.html" title="3. Java JMS Message Properties"></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. Apache Qpid JNDI Properties for AMQP Messaging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03.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="ch
 03s03.html">Next</a></td></tr></table><hr></div><div class="section" title="2. Apache Qpid JNDI Properties for AMQP Messaging"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="QpidJNDI"></a>2. Apache Qpid JNDI Properties for AMQP Messaging</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3.2. Apache Qpid JNDI Properties for AMQP Messaging</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="next" href="ch03s03.html" title="3.3. Java JMS Message Properties"></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.2. Apache Qpid JNDI Properties for AMQP Messaging</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03.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" hr
 ef="ch03s03.html">Next</a></td></tr></table><hr></div><div class="section" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="QpidJNDI"></a>3.2. Apache Qpid JNDI Properties for AMQP Messaging</h2></div></div></div><p>
 	Apache Qpid defines JNDI properties that can be used to specify JMS Connections and Destinations. Here is a typical JNDI properties file:
-      </p><div class="example"><a name="id2788980"></a><p class="title"><b>Example 3.3. JNDI Properties File</b></p><div class="example-contents"><pre class="programlisting">
+      </p><div class="example"><a name="id2588887"></a><p class="title"><b>Example 3.3. JNDI Properties File</b></p><div class="example-contents"><pre class="programlisting">
 java.naming.factory.initial 
   = org.apache.qpid.jndi.PropertiesFileInitialContextFactory
 
@@ -9,9 +9,9 @@ connectionfactory.qpidConnectionfactory 
   = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672'
 # destination.[jndiname] = [address_string]
 destination.topicExchange = amq.topic
-</pre></div></div><br class="example-break"><p>The following sections describe the JNDI properties that Qpid uses.</p><div class="section" title="2.1. JNDI Properties for Apache Qpid"><div class="titlepage"><div><div><h3 class="title"><a name="id2789002"></a>2.1. JNDI Properties for Apache Qpid</h3></div></div></div><p>
+</pre></div></div><br class="example-break"><p>The following sections describe the JNDI properties that Qpid uses.</p><div class="section" title="3.2.1. JNDI Properties for Apache Qpid"><div class="titlepage"><div><div><h3 class="title"><a name="id2588909"></a>3.2.1. JNDI Properties for Apache Qpid</h3></div></div></div><p>
 	  Apache Qpid supports the properties shown in the following table:
-        </p><div class="table"><a name="id2789012"></a><p class="title"><b>Table 3.1. JNDI Properties supported by Apache Qpid</b></p><div class="table-contents"><table summary="JNDI Properties supported by Apache Qpid" border="1"><colgroup><col><col></colgroup><thead><tr><th>
+        </p><div class="table"><a name="id2588919"></a><p class="title"><b>Table 3.1. JNDI Properties supported by Apache Qpid</b></p><div class="table-contents"><table summary="JNDI Properties supported by Apache Qpid" border="1"><colgroup><col><col></colgroup><thead><tr><th>
 		  Property
 	        </th><th>
 		  Purpose
@@ -41,12 +41,12 @@ destination.topicExchange = amq.topic
 		    queues, topics and header matching, using an
 		    address string.  
 
-		    <sup>[<a name="id2789097" href="#ftn.id2789097" class="footnote">a</a>]</sup>
+		    <sup>[<a name="id2589003" href="#ftn.id2589003" class="footnote">a</a>]</sup>
 		  </p>
-	        </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2789097" href="#id2789097" class="para">a</a>] </sup>Binding URLs, which were used in
+	        </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2589003" href="#id2589003" class="para">a</a>] </sup>Binding URLs, which were used in
 		    earlier versions of the Qpid Java JMS client, can
 		    still be used instead of address
-		    strings.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="2.2. Connection URLs"><div class="titlepage"><div><div><h3 class="title"><a name="id2789111"></a>2.2. Connection URLs</h3></div></div></div><p>
+		    strings.</p></div></td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="3.2.2. Connection URLs"><div class="titlepage"><div><div><h3 class="title"><a name="id2589017"></a>3.2.2. Connection URLs</h3></div></div></div><p>
 	  In JNDI properties, a Connection URL specifies properties for a connection. The format for a Connection URL is:
         </p><pre class="programlisting">amqp://[&lt;user&gt;:&lt;pass&gt;@][&lt;clientid&gt;]&lt;virtualhost&gt;[?&lt;option&gt;='&lt;value&gt;'[&amp;&lt;option&gt;='&lt;value&gt;']]
         </pre><p>
@@ -54,7 +54,7 @@ destination.topicExchange = amq.topic
         </p><pre class="programlisting">amqp://username:password@clientid/test?brokerlist='tcp://localhost:5672'
         </pre><p>
 	  Apache Qpid supports the following properties in Connection URLs:
-        </p><div class="table"><a name="id2789152"></a><p class="title"><b>Table 3.2. Connection URL Properties</b></p><div class="table-contents"><table summary="Connection URL Properties" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
+        </p><div class="table"><a name="id2589059"></a><p class="title"><b>Table 3.2. Connection URL Properties</b></p><div class="table-contents"><table summary="Connection URL Properties" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
 		  Option
 	        </th><th>
 		  Type
@@ -104,13 +104,13 @@ destination.topicExchange = amq.topic
         </p><pre class="programlisting">brokerlist='tcp://localhost:5672'
         </pre><p>
 	  A broker list can contain more than one broker address; if so, the connection is made to the first broker in the list that is available. In general, it is better to use the failover exchange when using multiple brokers, since it allows applications to fail over if a broker goes down.
-	</p><div class="example"><a name="id2789314"></a><p class="title"><b>Example 3.4. Broker Lists</b></p><div class="example-contents"><p>A broker list can specify properties to be used when connecting to the broker, such as security options. This broker list specifies options for a Kerberos connection using GSSAPI:</p><pre class="programlisting">
+	</p><div class="example"><a name="id2589220"></a><p class="title"><b>Example 3.4. Broker Lists</b></p><div class="example-contents"><p>A broker list can specify properties to be used when connecting to the broker, such as security options. This broker list specifies options for a Kerberos connection using GSSAPI:</p><pre class="programlisting">
 amqp://guest:guest@test/test?sync_ack='true'
     &amp;brokerlist='tcp://ip1:5672?sasl_mechs='GSSAPI'
 	</pre><p>This broker list specifies SSL options:</p><pre class="programlisting">
 amqp://guest:guest@test/test?sync_ack='true'
    &amp;brokerlist='tcp://ip1:5672?ssl='true'&amp;ssl_cert_alias='cert1'
-	</pre></div></div><br class="example-break"><p>The following broker list options are supported.</p><div class="table"><a name="id2789350"></a><p class="title"><b>Table 3.3. Broker List Options</b></p><div class="table-contents"><table summary="Broker List Options" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
+	</pre></div></div><br class="example-break"><p>The following broker list options are supported.</p><div class="table"><a name="id2589256"></a><p class="title"><b>Table 3.3. Broker List Options</b></p><div class="table-contents"><table summary="Broker List Options" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
 		  Option
 	        </th><th>
 		  Type
@@ -209,4 +209,4 @@ amqp://guest:guest@test/test?sync_ack='t
 
 	        </td><td>
           If multiple certificates are present in the keystore, the alias will be used to extract the correct certificate.
-	        </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Using the Qpid JMS client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3. Java JMS Message Properties</td></tr></table></div></body></html>
+	        </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Using the Qpid JMS client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.3. Java JMS Message Properties</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s03.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s03.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s03.html Fri Jul 23 16:48:11 2010
@@ -1,8 +1,8 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3. Java JMS Message Properties</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s02.html" title="2. Apache Qpid JNDI Properties for AMQP Messaging"><link rel="next" href="ch03s04.html" title="4. JMS MapMessage Types"></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. Java JMS Message Properties</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s02.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="ch03s04.html">Next</a></td></
 tr></table><hr></div><div class="section" title="3. Java JMS Message Properties"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2789620"></a>3. Java JMS Message Properties</h2></div></div></div><p>The following table shows how Qpid Messaging API message
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3.3. Java JMS Message Properties</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s02.html" title="3.2. Apache Qpid JNDI Properties for AMQP Messaging"><link rel="next" href="ch03s04.html" title="3.4. JMS MapMessage Types"></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.3. Java JMS Message Properties</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s02.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="ch03s04.html">Next</a
 ></td></tr></table><hr></div><div class="section" title="3.3. Java JMS Message Properties"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589526"></a>3.3. Java JMS Message Properties</h2></div></div></div><p>The following table shows how Qpid Messaging API message
         properties are mapped to AMQP 0-10 message properties and
         delivery properties. In this table <code class="varname">msg</code>
         refers to the Message class defined in the Qpid Messaging API,
         <code class="varname">mp</code> refers to an AMQP 0-10
         <code class="varname">message-properties</code> struct, and
         <code class="varname">dp</code> refers to an AMQP 0-10
-        <code class="varname">delivery-properties</code> struct.</p><div class="table"><a name="id2789650"></a><p class="title"><b>Table 3.4. Java JMS Mapping to AMQP 0-10 Message Properties</b></p><div class="table-contents"><table summary="Java JMS Mapping to AMQP 0-10 Message Properties" border="1"><colgroup><col><col></colgroup><thead><tr><th>Java JMS Message Property</th><th>AMQP 0-10 Property<sup>[<a name="id2789670" href="#ftn.id2789670" class="footnote">a</a>]</sup></th></tr></thead><tbody><tr><td>JMSMessageID</td><td>mp.message_id</td></tr><tr><td>qpid.subject<sup>[<a name="id2789704" href="#ftn.id2789704" class="footnote">b</a>]</sup></td><td>mp.application_headers["qpid.subject"]</td></tr><tr><td>JMSXUserID</td><td>mp.user_id</td></tr><tr><td>JMSReplyTo</td><td>mp.reply_to<sup>[<a name="id2789729" href="#ftn.id2789729" class="footnote">c</a>]</sup></td></tr><tr><td>JMSCorrelationID</td><td>mp.correlation_id</td></tr><tr><td>JMSDeliveryMode</td><td>dp.delivery_mo
 de</td></tr><tr><td>JMSPriority</td><td>dp.priority</td></tr><tr><td>JMSExpiration</td><td>dp.ttl<sup>[<a name="id2789767" href="#ftn.id2789767" class="footnote">d</a>]</sup></td></tr><tr><td>JMSRedelivered</td><td>dp.redelivered</td></tr><tr><td>JMS Properties</td><td>mp.application_headers</td></tr><tr><td>JMSType</td><td>mp.content_type</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2789670" href="#id2789670" class="para">a</a>] </sup>In these entries, <code class="literal">mp</code> refers to an AMQP message property, and <code class="literal">dp</code> refers to an AMQP delivery property.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2789704" href="#id2789704" class="para">b</a>] </sup>This is a custom JMS property, set automatically by the Java JMS client implementation.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2789729" href="#id2789729" class="para">c</a>] </sup>The reply_to is convert
 ed from the protocol representation into an address.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2789767" href="#id2789767" class="para">d</a>] </sup>JMSExpiration = dp.ttl + currentTime</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="ch03s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Apache Qpid JNDI Properties for AMQP Messaging </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4. JMS MapMessage Types</td></tr></table></div></body></html>
+        <code class="varname">delivery-properties</code> struct.</p><div class="table"><a name="id2589557"></a><p class="title"><b>Table 3.4. Java JMS Mapping to AMQP 0-10 Message Properties</b></p><div class="table-contents"><table summary="Java JMS Mapping to AMQP 0-10 Message Properties" border="1"><colgroup><col><col></colgroup><thead><tr><th>Java JMS Message Property</th><th>AMQP 0-10 Property<sup>[<a name="id2589577" href="#ftn.id2589577" class="footnote">a</a>]</sup></th></tr></thead><tbody><tr><td>JMSMessageID</td><td>mp.message_id</td></tr><tr><td>qpid.subject<sup>[<a name="id2589610" href="#ftn.id2589610" class="footnote">b</a>]</sup></td><td>mp.application_headers["qpid.subject"]</td></tr><tr><td>JMSXUserID</td><td>mp.user_id</td></tr><tr><td>JMSReplyTo</td><td>mp.reply_to<sup>[<a name="id2589635" href="#ftn.id2589635" class="footnote">c</a>]</sup></td></tr><tr><td>JMSCorrelationID</td><td>mp.correlation_id</td></tr><tr><td>JMSDeliveryMode</td><td>dp.delivery_mo
 de</td></tr><tr><td>JMSPriority</td><td>dp.priority</td></tr><tr><td>JMSExpiration</td><td>dp.ttl<sup>[<a name="id2589673" href="#ftn.id2589673" class="footnote">d</a>]</sup></td></tr><tr><td>JMSRedelivered</td><td>dp.redelivered</td></tr><tr><td>JMS Properties</td><td>mp.application_headers</td></tr><tr><td>JMSType</td><td>mp.content_type</td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2589577" href="#id2589577" class="para">a</a>] </sup>In these entries, <code class="literal">mp</code> refers to an AMQP message property, and <code class="literal">dp</code> refers to an AMQP delivery property.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2589610" href="#id2589610" class="para">b</a>] </sup>This is a custom JMS property, set automatically by the Java JMS client implementation.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2589635" href="#id2589635" class="para">c</a>] </sup>The reply_to is convert
 ed from the protocol representation into an address.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2589673" href="#id2589673" class="para">d</a>] </sup>JMSExpiration = dp.ttl + currentTime</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="ch03s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.2. Apache Qpid JNDI Properties for AMQP Messaging </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.4. JMS MapMessage Types</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s04.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s04.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s04.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4. JMS MapMessage Types</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s03.html" title="3. Java JMS Message Properties"><link rel="next" href="ch03s05.html" title="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">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="ch03s05.html">Next</a></td></tr></table><hr></div><div class="se
 ction" title="4. JMS MapMessage Types"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="section-JMS-MapMessage"></a>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="id2789822"></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=ISO-8859-1"><title>3.4. JMS MapMessage Types</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.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="ch03s05.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="ch03s05.html">Next</a></td></tr></table><hr></div><div c
 lass="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="id2589728"></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;
@@ -48,4 +48,4 @@ 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>&#8594; Python</th><th>&#8594; 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>u
 uid</td><td>qpid::types::Uuid</td></tr><tr><td>java.util.Map<sup>[<a name="id2789969" href="#ftn.id2789969" 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 name="ftn.id2789969" href="#id2789969" 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="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">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"> 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>&#8594; Python</th><th>&#8594; 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>u
 uid</td><td>qpid::types::Uuid</td></tr><tr><td>java.util.Map<sup>[<a name="id2589875" href="#ftn.id2589875" 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 name="ftn.id2589875" href="#id2589875" 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="ch03.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch03s05.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/0.7/Programming-In-Apache-Qpid/html/ch03s05.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s05.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s05.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch03s05.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3.5. JMS Client Logging</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s04.html" title="3.4. JMS MapMessage Types"><link rel="next" href="ch04.html" title="Chapter 4. Using the Qpid WCF 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="ch03s04.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="ch04.html">Next</a></td></tr></table><hr></div><div clas
 s="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 <a class="ulink" href="http://www.slf4j.org/" target="_top">SLF4J</a>. A user can place a slf4j binding of their choice in the classpath and configure the respective logging mechanism to suit their needs. Ex bindings include log4j, jdk1.4 logging ..etc</p><p>Following is an example on how to configure the client logging with the log4j binding.</p><p>For more information on how to configure log4j, please consult the log4j documentation.</p><p>If using the log4j binding please ensure to set the log level for org.apache.qpid explicitly. Otherwise log4j will default to DEBUG which will degrade performance considerably due to excessive logging. Recommended logging level for production is WARN.</p><div class="example"><a name="id3064816"></a><p 
 class="title"><b>Example 3.6. log4j Logging Properties</b></p><div class="example-contents"><p>You could place the snippet below in a log4j.properties file and place it in the classpath or explicitly specify it using the -Dlog4j.configuration property. The following configures the qpid client to log at the WARN level</p><pre class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3.5. JMS Client Logging</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch03.html" title="Chapter 3. Using the Qpid JMS client"><link rel="prev" href="ch03s04.html" title="3.4. JMS MapMessage Types"><link rel="next" href="ch04.html" title="Chapter 4. Using the Qpid WCF 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="ch03s04.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="ch04.html">Next</a></td></tr></table><hr></div><div clas
 s="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 following 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="id2589948"></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/0.7/Programming-In-Apache-Qpid/html/ch04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Using the Qpid WCF client</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="index.html" title="Programming in Apache Qpid"><link rel="prev" href="ch03s05.html" title="5. JMS Client Logging"><link rel="next" href="ch04s02.html" title="2. Endpoints"></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">Chapter 4. Using the Qpid WCF client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s05.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch04s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 4. Using the 
 Qpid WCF client"><div class="titlepage"><div><div><h2 class="title"><a name="QpidWCF"></a>Chapter 4. Using the Qpid WCF client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch04.html#id2790063">1. XML and Binary Bindings</a></span></dt><dt><span class="section"><a href="ch04s02.html">2. Endpoints</a></span></dt><dt><span class="section"><a href="ch04s03.html">3. Message Headers</a></span></dt><dt><span class="section"><a href="ch04s04.html">4. Security</a></span></dt><dt><span class="section"><a href="ch04s05.html">5. Transactions</a></span></dt></dl></div><div class="section" title="1. XML and Binary Bindings"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2790063"></a>1. XML and Binary Bindings</h2></div></div></div><p>The Qpid WCF client provides two bindings, each with support for
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Using the Qpid WCF client</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="index.html" title="Programming in Apache Qpid"><link rel="prev" href="ch03s05.html" title="3.5. JMS Client Logging"><link rel="next" href="ch04s02.html" title="4.2. Endpoints"></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">Chapter 4. Using the Qpid WCF client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch03s05.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch04s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 4. Using 
 the Qpid WCF client"><div class="titlepage"><div><div><h2 class="title"><a name="QpidWCF"></a>Chapter 4. Using the Qpid WCF client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch04.html#id2589975">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></div><div class="section" title="4.1. XML and Binary Bindings"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2589975"></a>4.1. XML and Binary Bindings</h2></div></div></div><p>The Qpid WCF client provides two bindings, each with support for
       Windows .NET transactions.</p><p>The AmqpBinding is suitable for communication between two WCF
       applications.  By default it uses the WCF binary .NET XML encoder
       (BinaryMessageEncodingBindingElement) for efficient message
@@ -6,7 +6,7 @@
       Optimization Mechanism (MTOM) encoders.  Here is a traditional service
       model sample program using the AmqpBinding.  It assumes that the queue
       "hello_service_node" has been created and configured on the AMQP
-      broker.</p><div class="example"><a name="id2790085"></a><p class="title"><b>Example 4.1. Traditional service model "Hello world!" example</b></p><div class="example-contents"><pre class="programlisting">
+      broker.</p><div class="example"><a name="id2589997"></a><p class="title"><b>Example 4.1. Traditional service model "Hello world!" example</b></p><div class="example-contents"><pre class="programlisting">
 namespace Apache.Qpid.Documentation.HelloService
 {
   using System;
@@ -90,7 +90,7 @@ namespace Apache.Qpid.Documentation.Hell
       AmqpBinding sample where the simple greeting is encapsulated in a
       compressed SOAP envelope, the wire representation of the message
       contains the raw content and is identical and fully interoperable with
-      the Qpid C++ "Hello world!"  example.</p><div class="example"><a name="id2790105"></a><p class="title"><b>Example 4.2. Binary  "Hello world!" example using the channel model</b></p><div class="example-contents"><pre class="programlisting">
+      the Qpid C++ "Hello world!"  example.</p><div class="example"><a name="id2590017"></a><p class="title"><b>Example 4.2. Binary  "Hello world!" example using the channel model</b></p><div class="example-contents"><pre class="programlisting">
 namespace Apache.Qpid.Samples.Channel.HelloWorld
 {
   using System;
@@ -180,7 +180,7 @@ namespace Apache.Qpid.Samples.Channel.He
 </pre></div></div><br class="example-break"><p>Bindings define ChannelFactories and ChannelListeners associated with
       an AMQP Broker.  WCF will frequently automatically create and manage
       the life cycle of a these and the resulting IChannel objects used in
-      message transfer.  The binding parameters that can be set are:</p><div class="table"><a name="id2790179"></a><p class="title"><b>Table 4.1. WCF Binding Parameters</b></p><div class="table-contents"><table summary="WCF Binding Parameters" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Parameter</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td>
+      message transfer.  The binding parameters that can be set are:</p><div class="table"><a name="id2590091"></a><p class="title"><b>Table 4.1. WCF Binding Parameters</b></p><div class="table-contents"><table summary="WCF Binding Parameters" width="100%" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Parameter</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td>
 		BrokerHost
 	      </td><td>
 		localhost
@@ -223,4 +223,4 @@ namespace Apache.Qpid.Samples.Channel.He
 		to medium sized SOAP based messages, buffered is
 		usually the preferred choice.  For binary messages,
 		streamed TransferMode is the more efficient mode.
-	      </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s05.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch04s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5. JMS Client Logging </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2. Endpoints</td></tr></table></div></body></html>
+	      </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch03s05.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch04s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.5. JMS Client Logging </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.2. Endpoints</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s02.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s02.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s02.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2. Endpoints</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="next" href="ch04s03.html" title="3. Message Headers"></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. Endpoints</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr></table><hr></div><div class="section" title="2. Endpoi
 nts"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2790352"></a>2. Endpoints</h2></div></div></div><p>In Qpid 0.6 the WCF Endpoints map to simple AMQP 0-10
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4.2. Endpoints</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="next" href="ch04s03.html" title="4.3. Message Headers"></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">4.2. Endpoints</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr></table><hr></div><div class="section" title="4.2.
  Endpoints"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2590264"></a>4.2. Endpoints</h2></div></div></div><p>In Qpid 0.6 the WCF Endpoints map to simple AMQP 0-10
       exchanges (IOutputChannel) or AMQP 0-10 queues (IInputChannel).
       The format for an IOutputChannel is</p><pre class="programlisting">
   "amqp:amq.direct" or "amqp:my_exchange?routingkey=my_routing_key"
@@ -8,4 +8,4 @@
       the particular channel.  Outgoing messages can always have their
       routing key uniquely set.</p><p>If the respective queue or exchange doesn't exist, an exception
       is thrown when opening the channel.  Queues and exchanges can be
-      created and configured using qpid-config.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Using the Qpid WCF client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3. Message Headers</td></tr></table></div></body></html>
+      created and configured using qpid-config.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Using the Qpid WCF client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.3. Message Headers</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s03.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s03.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s03.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3. Message Headers</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04s02.html" title="2. Endpoints"><link rel="next" href="ch04s04.html" title="4. Security"></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. Message Headers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s02.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch04s04.html">Next</a></td></tr></table><hr></div><div class="section" title="3. Message Headers"><di
 v class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2790393"></a>3. Message Headers</h2></div></div></div><p>AMQP specific message headers can be set on or retrieved
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4.3. Message Headers</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04s02.html" title="4.2. Endpoints"><link rel="next" href="ch04s04.html" title="4.4. Security"></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">4.3. Message Headers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s02.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch04s04.html">Next</a></td></tr></table><hr></div><div class="section" title="4.3. Message He
 aders"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2590305"></a>4.3. Message Headers</h2></div></div></div><p>AMQP specific message headers can be set on or retrieved
       from the ServiceModel.Channels.Message using the AmqpProperties
       type.</p><p>For example, on output:</p><pre class="programlisting">
 AmqpProperties props = new AmqpProperties();
@@ -16,4 +16,4 @@ public void SayHello(string greeting)
   AmqpString extra = (AmqpString) props.PropertyMap["my_custom_header"];
   Console.WriteLine("Service received: {0} and {1}", greeting, extra);
 }
-</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Endpoints </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4. Security</td></tr></table></div></body></html>
+</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.2. Endpoints </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.4. Security</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s04.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s04.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s04.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4. Security</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04s03.html" title="3. Message Headers"><link rel="next" href="ch04s05.html" title="5. Transactions"></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">4. Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s03.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch04s05.html">Next</a></td></tr></table><hr></div><div class="section" title="4. Security"><div class="ti
 tlepage"><div><div><h2 class="title" style="clear: both"><a name="id2787223"></a>4. Security</h2></div></div></div><p>To engage TLS/SSL:</p><pre class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4.4. Security</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04s03.html" title="4.3. Message Headers"><link rel="next" href="ch04s05.html" title="4.5. Transactions"></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">4.4. Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s03.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch04s05.html">Next</a></td></tr></table><hr></div><div class="section" title="4.4. Security"><div
  class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2590340"></a>4.4. Security</h2></div></div></div><p>To engage TLS/SSL:</p><pre class="programlisting">
 binding.Security.Mode = AmqpSecurityMode.Transport;
 binding.Security.Transport.UseSSL = true;
 binding.BrokerPort = 5671;
@@ -18,4 +18,4 @@ credentials.UserName.Password = "guest";
 bindingParameters = new BindingParameterCollection();
 bindingParameters.Add(credentials);
 readerFactory = binding.BuildChannelFactory&lt;IInputChannel&gt;(bindingParameters);
-</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3. Message Headers </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5. Transactions</td></tr></table></div></body></html>
+</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.3. Message Headers </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.5. Transactions</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s05.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s05.html?rev=967163&r1=967162&r2=967163&view=diff
==============================================================================
--- qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s05.html (original)
+++ qpid/site/docs/books/0.7/Programming-In-Apache-Qpid/html/ch04s05.html Fri Jul 23 16:48:11 2010
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>5. Transactions</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04s04.html" title="4. Security"></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">5. Transactions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s04.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> </td></tr></table><hr></div><div class="section" title="5. Transactions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2787267"></a>5. Transactions</h2>
 </div></div></div><p>The WCF channel provides a transaction resource manager
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4.5. Transactions</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Programming in Apache Qpid"><link rel="up" href="ch04.html" title="Chapter 4. Using the Qpid WCF client"><link rel="prev" href="ch04s04.html" title="4.4. Security"><link rel="next" href="ch05.html" title="Chapter 5. The .NET Binding for the C++ Messaging 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">4.5. Transactions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s04.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Using the Qpid WCF client</th><td width="20%" align="right"> <a accesskey="n" href="ch05.html">Next</a></td></tr></table><hr></div><div class="s
 ection" title="4.5. Transactions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2590383"></a>4.5. Transactions</h2></div></div></div><p>The WCF channel provides a transaction resource manager
       module and a recovery module that together provide distributed
       transaction support with one-phase optimization.  Some
       configuration is required on Windows machines to enable
@@ -40,4 +40,4 @@ using (TransactionScope ts = new Transac
    // increment ExactlyOnceSent counter on DB
    ts.Complete();
 }
-</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">4. Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
+</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.4. Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. The .NET Binding for the C++ Messaging Client</td></tr></table></div></body></html>



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message