You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by jo...@apache.org on 2011/02/02 23:58:38 UTC
svn commit: r1066676 [6/8] - in /qpid/site/docs/books/trunk:
AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/pdf/
AMQP-Messaging-Broker-Java-Book/html/ AMQP-Messaging-Broker-Java-Book/pdf/
Programming-In-Apache-Qpid/html/ Programmin...
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s02.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s02.html Wed Feb 2 22:58:35 2011
@@ -1,17 +1,17 @@
<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="id3084675"></a><p class="title"><b>Example 3.3. JNDI Properties File</b></p><div class="example-contents"><pre class="programlisting">
-java.naming.factory.initial
+ </p><div class="example"><a name="id2664921"></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
# connectionfactory.[jndiname] = [ConnectionURL]
-connectionfactory.qpidConnectionfactory
+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="3.2.1. JNDI Properties for Apache Qpid"><div class="titlepage"><div><div><h3 class="title"><a name="id3084697"></a>3.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="id2664943"></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="id3084707"></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="id2664953"></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
@@ -39,14 +39,14 @@ destination.topicExchange = amq.topic
<p>
Can be used for defining all amq destinations,
queues, topics and header matching, using an
- address string.
+ address string.
- <sup>[<a name="id3084791" href="#ftn.id3084791" class="footnote">a</a>]</sup>
+ <sup>[<a name="id2665037" href="#ftn.id2665037" class="footnote">a</a>]</sup>
</p>
- </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id3084791" href="#id3084791" 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.id2665037" href="#id2665037" 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="3.2.2. Connection URLs"><div class="titlepage"><div><div><h3 class="title"><a name="id3084806"></a>3.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="section-jms-connection-url"></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://[<user>:<pass>@][<clientid>]<virtualhost>[?<option>='<value>'[&<option>='<value>']]
</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="id3084847"></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="id2665094"></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="id3085009"></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="id2665256"></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'
&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'
&brokerlist='tcp://ip1:5672?ssl='true'&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="id3085044"></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="id2665292"></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
@@ -140,7 +140,7 @@ amqp://guest:guest@test/test?sync_ack='t
</td></tr><tr><td>
sasl_encryption
</td><td>
- Boolean
+ Boolean
</td><td>
If <code class="literal">sasl_encryption='true'</code>, the JMS client attempts to negotiate a security layer with the broker using GSSAPI to encrypt the connection. Note that for this to happen, GSSAPI must be selected as the sasl_mech.
</td></tr><tr><td>
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s03.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s03.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s03.html Wed Feb 2 22:58:35 2011
@@ -1,8 +1,8 @@
-<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="id3085314"></a>3.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="id2665562"></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="id3085345"></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="id3085365" href="#ftn.id3085365" 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="id3085398" href="#ftn.id3085398" 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="id3085423" href="#ftn.id3085423" 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="id3085462" href="#ftn.id3085462" 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.id3085365" href="#id3085365" 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.id3085398" href="#id3085398" 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.id3085423" href="#id3085423" 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.id3085462" href="#id3085462" 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>
+ <code class="varname">delivery-properties</code> struct.</p><div class="table"><a name="id2665592"></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="id2665612" href="#ftn.id2665612" 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="id2665646" href="#ftn.id2665646" 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="id2665670" href="#ftn.id2665670" 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="id2665709" href="#ftn.id2665709" 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.id2665612" href="#id2665612" 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.id2665646" href="#id2665646" 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.id2665670" href="#id2665670" 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.id2665709" href="#id2665709" 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/trunk/Programming-In-Apache-Qpid/html/ch03s04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s04.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s04.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s04.html Wed Feb 2 22:58:35 2011
@@ -1,4 +1,4 @@
-<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="id3085516"></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="id2665764"></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;
@@ -27,7 +27,7 @@ m.setDoubleProperty("price", 0.99);
List<String> colors = new ArrayList<String>();
colors.add("red");
colors.add("green");
-colors.add("white");
+colors.add("white");
m.setObject("colours", colors);
Map<String,Double> dimensions = new HashMap<String,Double>();
@@ -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>→ 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>u
uid</td><td>qpid::types::Uuid</td></tr><tr><td>java.util.Map<sup>[<a name="id3085663" href="#ftn.id3085663" 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.id3085663" href="#id3085663" 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>
+ </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>u
uid</td><td>qpid::types::Uuid</td></tr><tr><td>java.util.Map<sup>[<a name="id2665911" href="#ftn.id2665911" 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.id2665911" href="#id2665911" 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/trunk/Programming-In-Apache-Qpid/html/ch03s05.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s05.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s05.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s05.html Wed Feb 2 22:58:35 2011
@@ -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 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="id3085736"></a><p class="title"><b>Example 3.6. log4j Logging Properties</b></p><div class="example-contents"><pre class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=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="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="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="ch03s06.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="id2665983"></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
@@ -6,4 +6,4 @@ log4j.appender.console=org.apache.log4j.
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="ch03s04.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="ch04.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"> Chapter 4. Using the Qpid WCF client</td></tr></table></div></body></html>
+</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="ch03s04.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="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/ch04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04.html Wed Feb 2 22:58:35 2011
@@ -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="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#id3085763">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="id3085763"></a>4.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="ch03s06.html" title="3.6. Configuring the JMS Client"><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="ch03s06.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#id2667090">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="id2667090"></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="id3085785"></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="id2667112"></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="id3085805"></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="id2667132"></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;
@@ -102,7 +102,7 @@ namespace Apache.Qpid.Samples.Channel.He
using Apache.Qpid.Channel;
public class HelloWorld
- {
+ {
static void Main(string[] args)
{
String broker = "localhost";
@@ -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="id3085879"></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="id2667165"></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">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>
+ </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="ch03s06.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.6. Configuring the JMS Client </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/trunk/Programming-In-Apache-Qpid/html/ch04s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s02.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s02.html Wed Feb 2 22:58:35 2011
@@ -1,4 +1,4 @@
-<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="id3086052"></a>4.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="id2667401"></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"
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s03.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s03.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s03.html Wed Feb 2 22:58:35 2011
@@ -1,4 +1,4 @@
-<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="id3086093"></a>4.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="id2667442"></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();
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s04.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s04.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s04.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s04.html Wed Feb 2 22:58:35 2011
@@ -1,4 +1,4 @@
-<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="id3086128"></a>4.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="id2667477"></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;
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s05.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s05.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s05.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s05.html Wed Feb 2 22:58:35 2011
@@ -1,4 +1,4 @@
-<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="id3086171"></a>4.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="id2667533"></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
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05.html Wed Feb 2 22:58:35 2011
@@ -1,17 +1,15 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. The .NET Binding for the C++ Messaging 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="ch04s05.html" title="4.5. Transactions"><link rel="next" href="ch05s02.html" title="5.2. .NET Binding for the C++ Messaging Client Examples"></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 5. The .NET Binding for the C++ Messaging Client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s05.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch05s02.html">Next</a>
</td></tr></table><hr></div><div class="chapter" title="Chapter 5. The .NET Binding for the C++ Messaging Client"><div class="titlepage"><div><div><h2 class="title"><a name="id3086234"></a>Chapter 5. The .NET Binding for the C++ Messaging Client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch05.html#id3086261">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#id3086842">5.3.1. .NET Binding for the C++ Messaging API Class: Address</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3087449">5.3.2. .NET Binding for the C++ Messaging API Class: Connection</a></span>
</dt><dt><span class="section"><a href="ch05s03.html#id3088095">5.3.3. .NET Binding for the C++ Messaging API Class: Duration</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3088519">5.3.4. .NET Binding for the C++ Messaging API Class: FailoverUpdates</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3088698">5.3.5. .NET Binding for the C++ Messaging API Class: Message</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3089897">5.3.6. .NET Binding for the C++ Messaging API Class: Receiver</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3090543">5.3.7. .NET Binding for the C++ Messaging API Class: Sender</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3091022">5.3.8. .NET Binding for the C++ Messaging API Class: Session</a></span></dt><dt><span class="section"><a href="ch05s03.html#id3091987">5.3.9. .NET Binding for the C++ Messaging API Class: SessionReceiver</a></span></dt></dl></dd></dl></div><
p>
- The .NET Binding for the C++ Qpid Messaging Client is an intermediary program designed
- to make access to C++ Qpid Messaging methods simple and in a way familiar to the programmer.
- The .NET Binding creates and manipulates actual C++ Qpid Messaging API objects so that a .NET
- program will operate the same as if the program were written in native C++.
- </p><div class="section" title="5.1. .NET Binding for the C++ Messaging Client Component Architecture"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3086261"></a>5.1. .NET Binding for the C++ Messaging Client Component Architecture</h2></div></div></div><pre class="programlisting">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. The .NET Binding for the C++ Messaging 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="ch04s05.html" title="4.5. Transactions"><link rel="next" href="ch05s02.html" title="5.2. .NET Binding for the C++ Messaging Client Examples"></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 5. The .NET Binding for the C++ Messaging Client</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s05.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch05s02.html">Next</a>
</td></tr></table><hr></div><div class="chapter" title="Chapter 5. The .NET Binding for the C++ Messaging Client"><div class="titlepage"><div><div><h2 class="title"><a name="id2667595"></a>Chapter 5. The .NET Binding for the C++ Messaging Client</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch05.html#id2667619">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#id2668207">5.3.1. .NET Binding for the C++ Messaging API Class: Address</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2668818">5.3.2. .NET Binding for the C++ Messaging API Class: Connection</a></span>
</dt><dt><span class="section"><a href="ch05s03.html#id2669468">5.3.3. .NET Binding for the C++ Messaging API Class: Duration</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2669895">5.3.4. .NET Binding for the C++ Messaging API Class: FailoverUpdates</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2670078">5.3.5. .NET Binding for the C++ Messaging API Class: Message</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2671281">5.3.6. .NET Binding for the C++ Messaging API Class: Receiver</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2671931">5.3.7. .NET Binding for the C++ Messaging API Class: Sender</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2672414">5.3.8. .NET Binding for the C++ Messaging API Class: Session</a></span></dt><dt><span class="section"><a href="ch05s03.html#id2673383">5.3.9. .NET Binding Class: SessionReceiver</a></span></dt></dl></dd></dl></div><p>
+ The .NET Binding for the C++ Qpid Messaging Client is a library that gives
+ any .NET program access to Qpid C++ Messaging objects and methods.
+ </p><div class="section" title="5.1. .NET Binding for the C++ Messaging Client Component Architecture"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2667619"></a>5.1. .NET Binding for the C++ Messaging Client Component Architecture</h2></div></div></div><pre class="programlisting">
+----------------------------+
- | Dotnet examples |
+ | Dotnet examples |
| Managed C# |
+------+---------------+-----+
| |
V |
+---------------------------+ |
- | Managed Callback | |
+ | .NET Managed Callback | |
| org.apache.qpid.messaging.| |
| sessionreceiver.dll | |
+----------------------+----+ |
@@ -33,13 +31,11 @@ unmanaged | org.apache.qpid
| QPID Messaging C++ Libraries |
| qpid*.dll qmf*.dll |
+--------+--------------+----------+
-</pre>
-This diagram illustrates the code and library components of the binding
-and the hierarchical relationships between them.
-
- <div class="table"><a name="table-Dotnet-Binding-Component-Architecture"></a><p class="title"><b>Table 5.1. .NET Binding for the C++ Messaging Client Component Architecture</b></p><div class="table-contents"><table summary=".NET Binding for the C++ Messaging Client Component Architecture" border="1"><colgroup><col><col></colgroup><thead><tr><th>Component Name</th><th>Component Function</th></tr></thead><tbody><tr><td>QPID Messaging C++ Libraries</td><td>The QPID Messaging C++ core run time system</td></tr><tr><td>Unmanaged C++ Example Source Programs</td><td>Ordinary C++ programs that illustrate using qpid/cpp Messaging directly
- in a native Windows environment.</td></tr><tr><td>.NET Messaging Binding Library</td><td>The .NET Messaging library provides interoprability between managed .NET
- programs and the unmanaged, native Messaging C++ run time system. .NET programs
- create a Reference to this library thereby exposing all of the native C++
- Messaging functionality to programs written in any .NET language.</td></tr><tr><td>.NET Messaging Managed Callback Library</td><td>An extension of the .NET Messaging Binding Library that provides message
- callbacks in a managed .NET environment. This component is written purely in C#.</td></tr><tr><td>Managed C# .NET Example Source Programs</td><td>Various C# example programs that illustrate using .NET Messaging Binding in the .NET environment.</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="ch04s05.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch05s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.5. Transactions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.2. .NET Binding for the C++ Messaging Client Examples</td></tr></table></div></body></html>
+</pre><p>This diagram illustrates the code and library components of the binding
+and the hierarchical relationships between them.</p><div class="table"><a name="table-Dotnet-Binding-Component-Architecture"></a><p class="title"><b>Table 5.1. .NET Binding for the C++ Messaging Client Component Architecture</b></p><div class="table-contents"><table summary=".NET Binding for the C++ Messaging Client Component Architecture" border="1"><colgroup><col><col></colgroup><thead><tr><th>Component Name</th><th>Component Function</th></tr></thead><tbody><tr><td>QPID Messaging C++ Libraries</td><td>The QPID Messaging C++ core run time system</td></tr><tr><td>Unmanaged C++ Example Source Programs</td><td>Ordinary C++ programs that illustrate using qpid/cpp Messaging directly
+ in a native Windows environment.</td></tr><tr><td>.NET Messaging Binding Library</td><td>The .NET Messaging Binding library provides interoprability between
+ managed .NET programs and the unmanaged, native Qpid Messaging C++ core
+ run time system. .NET programs create a Reference to this library thereby
+ exposing all of the native C++ Messaging functionality to programs
+ written in any .NET language.</td></tr><tr><td>.NET Messaging Managed Callback Library</td><td>An extension of the .NET Messaging Binding Library that provides message
+ callbacks in a managed .NET environment.</td></tr><tr><td>Managed C# .NET Example Source Programs</td><td>Various C# example programs that illustrate using .NET Binding for C++ Messaging in the .NET environment.</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="ch04s05.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch05s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.5. Transactions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.2. .NET Binding for the C++ Messaging Client Examples</td></tr></table></div></body></html>
Modified: qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s02.html (original)
+++ qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s02.html Wed Feb 2 22:58:35 2011
@@ -1,22 +1,18 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>5.2. .NET Binding for the C++ Messaging Client Examples</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="ch05.html" title="Chapter 5. The .NET Binding for the C++ Messaging Client"><link rel="prev" href="ch05.html" title="Chapter 5. The .NET Binding for the C++ Messaging Client"><link rel="next" href="ch05s03.html" title="5.3. .NET Binding Class Mapping to Underlying C++ Messaging API"></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.2. .NET Binding for the C++ Messaging Client Examples</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Th
e .NET Binding for the C++ Messaging Client</th><td width="20%" align="right"> <a accesskey="n" href="ch05s03.html">Next</a></td></tr></table><hr></div><div class="section" title="5.2. .NET Binding for the C++ Messaging Client Examples"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3086394"></a>5.2. .NET Binding for the C++ Messaging Client Examples</h2></div></div></div>
-
- This chapter describes the various sample programs that are available to
- illustrate common Qpid Messaging usage.
-
- <div class="table"><a name="table-Dotnet-Binding-Example-Client-Server"></a><p class="title"><b>Table 5.2. Example : Client - Server</b></p><div class="table-contents"><table summary="Example : Client - Server" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Client - Server</th></tr></thead><tbody><tr><td>csharp.example.server</td><td>Creates a Receiver and listens for messages.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>5.2. .NET Binding for the C++ Messaging Client Examples</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="ch05.html" title="Chapter 5. The .NET Binding for the C++ Messaging Client"><link rel="prev" href="ch05.html" title="Chapter 5. The .NET Binding for the C++ Messaging Client"><link rel="next" href="ch05s03.html" title="5.3. .NET Binding Class Mapping to Underlying C++ Messaging API"></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.2. .NET Binding for the C++ Messaging Client Examples</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Th
e .NET Binding for the C++ Messaging Client</th><td width="20%" align="right"> <a accesskey="n" href="ch05s03.html">Next</a></td></tr></table><hr></div><div class="section" title="5.2. .NET Binding for the C++ Messaging Client Examples"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2667753"></a>5.2. .NET Binding for the C++ Messaging Client Examples</h2></div></div></div><p>This chapter describes the various sample programs that
+ are available to illustrate common Qpid Messaging usage.</p><div class="table"><a name="table-Dotnet-Binding-Example-Client-Server"></a><p class="title"><b>Table 5.2. Example : Client - Server</b></p><div class="table-contents"><table summary="Example : Client - Server" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.example.server</td><td>Creates a Receiver and listens for messages.
Upon message reception the message content is converted to upper case
and forwarded to the received message's ReplyTo address.</td></tr><tr><td>csharp.example.client</td><td>Sends a series of messages to the Server and prints the original message
- content and the received message content.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-MapSender-MapReceiver"></a><p class="title"><b>Table 5.3. Example : Map Sender – Map Receiver</b></p><div class="table-contents"><table summary="Example : Map Sender – Map Receiver" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Map Sender - Map Receiver</th></tr></thead><tbody><tr><td>csharp.map.receiver</td><td>Creates a Receiver and listens for a map message.
+ content and the received message content.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-MapSender-MapReceiver"></a><p class="title"><b>Table 5.3. Example : Map Sender – Map Receiver</b></p><div class="table-contents"><table summary="Example : Map Sender – Map Receiver" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.map.receiver</td><td>Creates a Receiver and listens for a map message.
Upon message reception the message is decoded and displayed on the console.</td></tr><tr><td>csharp.map.sender</td><td>Creates a map message and sends it to map.receiver.
The map message contains values for every supported .NET Messaging
- Binding data type.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-Spout-Drain"></a><p class="title"><b>Table 5.4. Example : Spout - Drain</b></p><div class="table-contents"><table summary="Example : Spout - Drain" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Spout - Drain</th></tr></thead><tbody><tr><td>csharp.example.spout</td><td>Spout is a more complex example of code that generates a series of messages
+ Binding data type.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-Spout-Drain"></a><p class="title"><b>Table 5.4. Example : Spout - Drain</b></p><div class="table-contents"><table summary="Example : Spout - Drain" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.example.spout</td><td>Spout is a more complex example of code that generates a series of messages
and sends them to peer program Drain. Flexible command line arguments allow
the user to specify a variety of message and program options.</td></tr><tr><td>csharp.example.drain</td><td>Drain is a more complex example of code that receives a series of messages
- and displays their contents on the console.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-CallbackSender-CallbackReceiver"></a><p class="title"><b>Table 5.5. Example : Map Callback Sender – Map Callback Receiver</b></p><div class="table-contents"><table summary="Example : Map Callback Sender – Map Callback Receiver" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Map Callback Sender - Map Callback Receiver</th></tr></thead><tbody><tr><td>csharp.map.callback.receiver</td><td>Creates a Receiver and listens for a map message.
+ and displays their contents on the console.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-CallbackSender-CallbackReceiver"></a><p class="title"><b>Table 5.5. Example : Map Callback Sender – Map Callback Receiver</b></p><div class="table-contents"><table summary="Example : Map Callback Sender – Map Callback Receiver" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.map.callback.receiver</td><td>Creates a Receiver and listens for a map message.
Upon message reception the message is decoded and displayed on the console.
This example illustrates the use of the C# managed code callback mechanism
provided by .NET Messaging Binding Managed Callback Library.</td></tr><tr><td>csharp.map.callback.sender</td><td>Creates a map message and sends it to map_receiver.
The map message contains values for every supported .NET Messaging
- Binding data type.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-DeclareQueues"></a><p class="title"><b>Table 5.6. Example - Declare Queues</b></p><div class="table-contents"><table summary="Example - Declare Queues" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Declare Queues</th></tr></thead><tbody><tr><td>csharp.example.declare_queues</td><td>A program to illustrate creating objects on a broker.
- This program creates a queue used by spout and drain.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-DirectSender-DirectReceiver"></a><p class="title"><b>Table 5.7. Example: Direct Sender - Direct Receiver</b></p><div class="table-contents"><table summary="Example: Direct Sender - Direct Receiver" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Direct Sender - Direct Receiver</th></tr></thead><tbody><tr><td>csharp.direct.receiver</td><td>Creates a Receiver and listens for a messages.
- Upon message reception the message is decoded and displayed on the console.</td></tr><tr><td>csharp.direct.sender</td><td> Creates a series of messages and sends them to csharp.direct.receiver.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-Helloworld"></a><p class="title"><b>Table 5.8. Example: Hello World</b></p><div class="table-contents"><table summary="Example: Hello World" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example</th><th>Hello World</th></tr></thead><tbody><tr><td>csharp.example.helloworld</td><td>A program to send a message and to receive the same message.</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="ch05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td><td width="40%" alig
n="right"> <a accesskey="n" href="ch05s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. The .NET Binding for the C++ Messaging Client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.3. .NET Binding Class Mapping to Underlying C++ Messaging API</td></tr></table></div></body></html>
+ Binding data type.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-DeclareQueues"></a><p class="title"><b>Table 5.6. Example - Declare Queues</b></p><div class="table-contents"><table summary="Example - Declare Queues" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.example.declare_queues</td><td>A program to illustrate creating objects on a broker.
+ This program creates a queue used by spout and drain.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-DirectSender-DirectReceiver"></a><p class="title"><b>Table 5.7. Example: Direct Sender - Direct Receiver</b></p><div class="table-contents"><table summary="Example: Direct Sender - Direct Receiver" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.direct.receiver</td><td>Creates a Receiver and listens for a messages.
+ Upon message reception the message is decoded and displayed on the console.</td></tr><tr><td>csharp.direct.sender</td><td> Creates a series of messages and sends them to csharp.direct.receiver.</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="table-Dotnet-Binding-Example-Helloworld"></a><p class="title"><b>Table 5.8. Example: Hello World</b></p><div class="table-contents"><table summary="Example: Hello World" border="1"><colgroup><col><col></colgroup><thead><tr><th>Example Name</th><th>Example Description</th></tr></thead><tbody><tr><td>csharp.example.helloworld</td><td>A program to send a message and to receive the same message.</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="ch05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td><td wid
th="40%" align="right"> <a accesskey="n" href="ch05s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. The .NET Binding for the C++ Messaging Client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.3. .NET Binding Class Mapping to Underlying C++ Messaging API</td></tr></table></div></body></html>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org