qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kw...@apache.org
Subject svn commit: r1576538 [12/13] - in /qpid/site: docs/ docs/components/qpid-jms/ docs/releases/qpid-0.26/ docs/releases/qpid-0.26/java-broker/ docs/releases/qpid-0.26/java-broker/book/ docs/releases/qpid-0.26/jms-client-0-8/ docs/releases/qpid-0.26/jms-cl...
Date Tue, 11 Mar 2014 22:52:45 GMT
Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html Tue Mar 11 22:52:42 2014
@@ -124,7 +124,7 @@
           Queue names may consist of any mixture of digits, letters, and underscores </p></li><li class="listitem"><p><span class="emphasis"><em>Options</em></span>, key-value pairs separated by '=' character specifying
           queue and exchange creation arguments, routing key, client behaviour, etc. </p></li></ul></div><p>
   </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Binding URL option quoting</h3><p>Take care with the quoting surrounding option values. Each option value
-        <span class="emphasis"><em>must</em></span> be surrounded with single quotes ('). </p></div><p> The following <span class="emphasis"><em>Binding URL</em></span> options are currently defined: </p><div class="table"><a id="idp2645888"></a><p class="title"><strong>Table&#160;8.1.&#160;Binding URL options </strong></p><div class="table-contents"><table border="1" summary="Binding URL options " width="100%"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Option</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><p>durable</p></td><td><p>boolean </p></td><td><p>Queue durability flag. If it is set to <span class="emphasis"><em>true</em></span>, a durable
+        <span class="emphasis"><em>must</em></span> be surrounded with single quotes ('). </p></div><p> The following <span class="emphasis"><em>Binding URL</em></span> options are currently defined: </p><div class="table"><a id="idp669056"></a><p class="title"><strong>Table&#160;8.1.&#160;Binding URL options </strong></p><div class="table-contents"><table border="1" summary="Binding URL options " width="100%"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Option</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><p>durable</p></td><td><p>boolean </p></td><td><p>Queue durability flag. If it is set to <span class="emphasis"><em>true</em></span>, a durable
                 queue is requested to create. The durable queue should be stored on the Broker and
                 remained there after Broker restarts until it is explicitly deleted. This option has
                 no meaning for JMS topic destinations, as by nature a topic destination only exists
@@ -155,7 +155,7 @@ direct://amq.direct//&lt;Queue Name&gt;
       </p><p>The Binding URLs for destinations created with calls to
           <span class="emphasis"><em>Session.createQueue(String)</em></span> can be expressed as </p><pre class="screen">
 direct://amq.direct//&lt;Queue Name&gt;?durable='true'
-         </pre><p> The durability flag is set to <span class="emphasis"><em>true</em></span> in such destinations. </p><div class="example"><a id="idp215984"></a><p class="title"><strong>Example&#160;8.1.&#160;Binding URL examples for JMS queues</strong></p><div class="example-contents"><pre class="screen">
+         </pre><p> The durability flag is set to <span class="emphasis"><em>true</em></span> in such destinations. </p><div class="example"><a id="idp725072"></a><p class="title"><strong>Example&#160;8.1.&#160;Binding URL examples for JMS queues</strong></p><div class="example-contents"><pre class="screen">
 direct://amq.direct//myNonDurableQueue
 direct://amq.direct//myDurableQueue?durable='true'
 direct://amq.direct//myAnotherQueue?durable='true'&amp;routingkey='myqueue'
@@ -167,7 +167,7 @@ direct://custom.direct//yetAnotherQueue
 topic://amq.topic//&lt;Queue name&gt;?routingkey='&lt;Topic Name&gt;'&amp;exclusive='true'&amp;autodelete='true'
          </pre><p>
       </p><p>The Binding URLs for a topic destination created with calls to
-          <span class="emphasis"><em>Session.createTopic("hello")</em></span> is provided below: </p><div class="example"><a id="idp221536"></a><p class="title"><strong>Example&#160;8.2.&#160;Binding URL examples for JMS topics</strong></p><div class="example-contents"><pre class="screen">
+          <span class="emphasis"><em>Session.createTopic("hello")</em></span> is provided below: </p><div class="example"><a id="idp6016176"></a><p class="title"><strong>Example&#160;8.2.&#160;Binding URL examples for JMS topics</strong></p><div class="example-contents"><pre class="screen">
 topic://amq.topic/hello/tmp_127_0_0_1_36973_1?routingkey='hello'&amp;exclusive='true'&amp;autodelete='true'
         </pre></div></div><p><br class="example-break" />
       </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="JMS-Client-0-8-Binding-URL-Topics-Wildcards"></a>8.1.3.&#160;Wildcard characters in routing keys for topic destinations</h3></div></div></div><p> AMQP exchanges of class <span class="emphasis"><em>topic</em></span> can route messages to the queues
@@ -181,7 +181,7 @@ topic://amq.topic?routingkey='stocks.#'
 topic://amq.topic?routingkey='stocks.*.ibm'
 topic://amq.topic?routingkey='stocks.nyse.ibm'
         </pre><p>
-      </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="JMS-Client-0-8-Binding-URL-Extra-Examples"></a>8.1.4.&#160;More Examples</h3></div></div></div><div class="table"><a id="idp229296"></a><p class="title"><strong>Table&#160;8.2.&#160;Binding URL examples</strong></p><div class="table-contents"><table border="1" summary="Binding URL examples"><colgroup><col /><col /></colgroup><thead><tr><th>Binding URL</th><th>Description</th></tr></thead><tbody><tr><td><p>fanout://amq.fanout//myQueue</p></td><td><p>Binding URL binding queue "myQueue" to predefined "amq.fanout" exchange
+      </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="JMS-Client-0-8-Binding-URL-Extra-Examples"></a>8.1.4.&#160;More Examples</h3></div></div></div><div class="table"><a id="idp6023936"></a><p class="title"><strong>Table&#160;8.2.&#160;Binding URL examples</strong></p><div class="table-contents"><table border="1" summary="Binding URL examples"><colgroup><col /><col /></colgroup><thead><tr><th>Binding URL</th><th>Description</th></tr></thead><tbody><tr><td><p>fanout://amq.fanout//myQueue</p></td><td><p>Binding URL binding queue "myQueue" to predefined "amq.fanout" exchange
                   of class "fanout"</p></td></tr><tr><td><p>topic://custom.topic//anotherQueue?routingkey='aq'</p></td><td><p>Binding URL binding queue "anotherQueue" to the exchange with name
                   "custom.topic" of class "topic" using binding key "aq".</p></td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Connection-URL.html">Prev</a>&#160;</td><td align="center" width="20%">&#160;</td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-System-Properties.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter&#160;7.&#160;Connection URLs&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;Chapter&#160;9.&#160;System Properties</td></tr></table></div></div>
 

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html Tue Mar 11 22:52:42 2014
@@ -108,7 +108,7 @@
       <div id="-middle" class="panel">
         <ul id="-path-navigation"><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-trunk/index.html">Qpid Trunk</a></li><li><a href="/releases/qpid-trunk/jms-client-0-8/book/index.html">Qpid JMS Client for AMQP protocols 0-8, 0-9 and 0-9-1</a></li><li>5.3.&#160;Connection</li></ul>
         <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">5.3.&#160;Connection</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="JMS-Client-0-8-Client-Understanding-ConnectionFactory.html">Prev</a>&#160;</td><th align="center" width="60%">Chapter&#160;5.&#160;Understanding the Qpid JMS client</th><td align="right" width="20%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-Session.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a id="JMS-Client-0-8-Client-Understanding-Connection"></a>5.3.&#160;Connection</h2></div></div></div><p>A Connection represents an open communication channel between application and
-      Broker.</p><p>Connections are created from the ConnectionFactory <a class="footnote" href="#ftn.idp562272" id="idp562272"><sup class="footnote">[3]</sup></a>.</p><p>Each connection utilises a single TCP/IP connection between the process of the application
+      Broker.</p><p>Connections are created from the ConnectionFactory <a class="footnote" href="#ftn.idp2398176" id="idp2398176"><sup class="footnote">[3]</sup></a>.</p><p>Each connection utilises a single TCP/IP connection between the process of the application
       and the process of the Broker. The act of establishing a connection is therefore a relatively
       expensive operation. It is recommended that the same connection is used for a series of
       message interactions. Patterns utilising a connection per message should not be used. </p><p>The underlying TCP/IP connection remains open for the lifetime of the JMS connection. It
@@ -131,13 +131,13 @@
         each individual broker, and the delay between each connection attempt. Also note the use of
         the <span class="emphasis"><em>failover option</em></span>
         <code class="literal">cyclecount</code> to control the number of times the failover mechanism will
-        traverse the brokerlist.</p><div class="example"><a id="idp5851168"></a><p class="title"><strong>Example&#160;5.1.&#160;Connection URL configured for failover</strong></p><div class="example-contents"><pre class="screen">
+        traverse the brokerlist.</p><div class="example"><a id="idp5759456"></a><p class="title"><strong>Example&#160;5.1.&#160;Connection URL configured for failover</strong></p><div class="example-contents"><pre class="screen">
 amqp://username:password@clientid/test
             ?brokerlist='tcp://localhost:15672?retries='10'&amp;connectdelay='1000';tcp://localhost:25672?retries='10'&amp;connectdelay='1000''
             &amp;failover='roundrobin?cyclecount='20''
         </pre></div></div><br class="example-break" /><p>For full details see <a class="xref" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Chapter&#160;7, <em>Connection URLs</em></a></p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Note, that a single broker failover is enabled by default. If the failover behaviour is not desired it can be switched off
        by setting a failover option to <span class="emphasis"><em>nofailover</em></span> as in the example below
-       </p><div class="example"><a id="idp5854912"></a><p class="title"><strong>Example&#160;5.2.&#160;Connection URL configured with nofailover</strong></p><div class="example-contents"><pre class="screen">
+       </p><div class="example"><a id="idp5763056"></a><p class="title"><strong>Example&#160;5.2.&#160;Connection URL configured with nofailover</strong></p><div class="example-contents"><pre class="screen">
 amqp://username:password@clientid/test
             ?brokerlist='tcp://localhost:15672?failover='nofailover'
         </pre></div></div><p><br class="example-break" />
@@ -151,22 +151,22 @@ amqp://username:password@clientid/test
         an application level heartbeat either in addition to, or instead of the heartbeat.</p><p>If the client ever fails to receive two consecutive heartbeats, the Connection will be
         automatically closed and the Connection's <a class="ulink" href="http://docs.oracle.com/javaee/6/api/javax/jms/ExceptionListener.html" target="_top">ExceptionListener</a> will
         receive a JMSException with a linked exception of AMQDisconnectedException. Any further use
-        of the JMS objects (Connection, Session etc), will results in a <a class="ulink" href="http://docs.oracle.com/javaee/6/api/javax/jms/IllegalStateException.html" target="_top">IllegalStateException</a>.</p><p>To enable heartbeating either use a Connection URL including the broker option <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-Heartbeat"><code class="literal">heartbeat</code></a>, or use the system property <a class="link" href="JMS-Client-0-8-System-Properties.html#JMS-Client-0-8-System-Properties-Heartbeat"><code class="literal">qpid.heartbeat</code></a>. </p><div class="example"><a id="idp1451120"></a><p class="title"><strong>Example&#160;5.3.&#160;Connection URL configured for heartbeating</strong></p><div class="example-contents"><pre class="screen">
+        of the JMS objects (Connection, Session etc), will results in a <a class="ulink" href="http://docs.oracle.com/javaee/6/api/javax/jms/IllegalStateException.html" target="_top">IllegalStateException</a>.</p><p>To enable heartbeating either use a Connection URL including the broker option <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-Heartbeat"><code class="literal">heartbeat</code></a>, or use the system property <a class="link" href="JMS-Client-0-8-System-Properties.html#JMS-Client-0-8-System-Properties-Heartbeat"><code class="literal">qpid.heartbeat</code></a>. </p><div class="example"><a id="idp2297760"></a><p class="title"><strong>Example&#160;5.3.&#160;Connection URL configured for heartbeating</strong></p><div class="example-contents"><pre class="screen">
 amqp://guest:guest@clientid/?brokerlist='localhost:5672?heartbeat='5''
         </pre></div></div><br class="example-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="JMS-Client-0-8-Client-Understanding-Connection-SSL"></a>5.3.3.&#160;SSL</h3></div></div></div><p>The Qpid JMS client supports connections encrypted using Secure Socket Layer (SSL) and
         SSL-Client Authentication. SSL is configured using Connection URL. To use SSL, SSL must be
         be configured on the Broker.</p><p>Some example Connection URLs using SSL follow:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Simple SSL when the Broker is secured by a certificate that is signed by a CA which
-            is trusted by the JVM.</p><div class="example"><a id="idp1456000"></a><p class="title"><strong>Example&#160;5.4.&#160;Connection URL configured for SSL - CA trusted by JVM</strong></p><div class="example-contents"><pre class="screen">
+            is trusted by the JVM.</p><div class="example"><a id="idp2302640"></a><p class="title"><strong>Example&#160;5.4.&#160;Connection URL configured for SSL - CA trusted by JVM</strong></p><div class="example-contents"><pre class="screen">
 amqp://guest:guest@clientid/?brokerlist='localhost:5671'&amp;ssl='true'
             </pre></div></div><br class="example-break" /></li><li class="listitem"><p>SSL when the Broker is secured by a certificate that is signed by a CA which is NOT
             trusted by the JVM (such as when a organisation is using a private CA, or self-signed
             certificates are in use). For this case, we use <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-TrustStore"><code class="literal">trust_store</code></a> and <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-TrustStorePassword"><code class="literal">trust_store_password</code></a> to specify a path a truststore file
-            (containing the certificate of the private-CA) and the truststore password.</p><div class="example"><a id="idp5946816"></a><p class="title"><strong>Example&#160;5.5.&#160;Connection URL configured for SSL - CA not trusted by JVM</strong></p><div class="example-contents"><pre class="screen">
+            (containing the certificate of the private-CA) and the truststore password.</p><div class="example"><a id="idp6150448"></a><p class="title"><strong>Example&#160;5.5.&#160;Connection URL configured for SSL - CA not trusted by JVM</strong></p><div class="example-contents"><pre class="screen">
 amqp://guest:guest@clientid/?brokerlist='localhost:5671?trust_store='/path/to/acme_org_ca.ts'&amp;trust_store_password='secret''&amp;ssl='true'
             </pre></div></div><br class="example-break" /></li><li class="listitem"><p>SSL with SSL client-auth. For this case, we use <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-KeyStore"><code class="literal">key_store</code></a> and <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-KeyStorePassword"><code class="literal">key_store_password</code></a> to specify a path a keystore file
-            (containing the certificate of the client) and the keystore password.</p><div class="example"><a id="idp5951824"></a><p class="title"><strong>Example&#160;5.6.&#160;Connection URL configured for SSL - SSL client-auth</strong></p><div class="example-contents"><pre class="screen">
+            (containing the certificate of the client) and the keystore password.</p><div class="example"><a id="idp6155456"></a><p class="title"><strong>Example&#160;5.6.&#160;Connection URL configured for SSL - SSL client-auth</strong></p><div class="example-contents"><pre class="screen">
 amqp://guest:guest@clientid/?brokerlist='localhost:5671?trust_store='/path/to/app1_client_cert.ks'&amp;key_store_password='secret''&amp;ssl='true'
-            </pre></div></div><br class="example-break" /></li></ul></div></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp562272"><p><a class="para" href="#idp562272"><sup class="para">[3] </sup></a>Constructors of the AMQConnection class must not be used.</p></div></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Client-Understanding-ConnectionFactory.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Client-Understanding.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-Session.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">5.2.&#160;ConnectionFactory&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.4.&#160;
 Session</td></tr></table></div></div>
+            </pre></div></div><br class="example-break" /></li></ul></div></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp2398176"><p><a class="para" href="#idp2398176"><sup class="para">[3] </sup></a>Constructors of the AMQConnection class must not be used.</p></div></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Client-Understanding-ConnectionFactory.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Client-Understanding.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-Session.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">5.2.&#160;ConnectionFactory&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.4.&#16
 0;Session</td></tr></table></div></div>
 
         <hr/>
 

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html Tue Mar 11 22:52:42 2014
@@ -112,7 +112,7 @@
       InitialContext is itself obtained from an InitialContextFactory. </p><p>The Qpid JMS client provides a single implementation of the InitialContextFactory in class
         <code class="literal">org.apache.qpid.jndi.PropertiesFileInitialContextFactory</code>. This
       implementation is backed by a <a class="ulink" href="http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html" target="_top">Properties</a> object which can of course be loaded from an external properties file,
-      or created programatically.</p><p>The examples in the previous chapter illustrated the Java code required to <a class="link" href="JMS-Client-0-8-Examples.html#JMS-Client-0-8-Examples-PTP" title="4.1.&#160;Point to point example">create the InitialContext</a> and an <a class="link" href="JMS-Client-0-8-Examples.html#JMS-Client-0-8-Examples-PTP-PropertiesFile" title="Example&#160;4.2.&#160;JMS Example - Point to Point Messaging - JNDI Properties">example properties file</a>.</p><p>Note that the Qpid Broker does not present a JNDI interface to the application.</p><div class="figure"><a id="idp585392"></a><p class="title"><strong>Figure&#160;5.2.&#160;JNDI overview</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="JNDI overview" src="images/JndiOverview.png" /></div></div></div><br class="figure-break" /></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-
 8-Client-Understanding.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Client-Understanding.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-Connection.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter&#160;5.&#160;Understanding the Qpid JMS client&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.3.&#160;Connection</td></tr></table></div></div>
+      or created programatically.</p><p>The examples in the previous chapter illustrated the Java code required to <a class="link" href="JMS-Client-0-8-Examples.html#JMS-Client-0-8-Examples-PTP" title="4.1.&#160;Point to point example">create the InitialContext</a> and an <a class="link" href="JMS-Client-0-8-Examples.html#JMS-Client-0-8-Examples-PTP-PropertiesFile" title="Example&#160;4.2.&#160;JMS Example - Point to Point Messaging - JNDI Properties">example properties file</a>.</p><p>Note that the Qpid Broker does not present a JNDI interface to the application.</p><div class="figure"><a id="idp1897824"></a><p class="title"><strong>Figure&#160;5.2.&#160;JNDI overview</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="JNDI overview" src="images/JndiOverview.png" /></div></div></div><br class="figure-break" /></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0
 -8-Client-Understanding.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Client-Understanding.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-Connection.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter&#160;5.&#160;Understanding the Qpid JMS client&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.3.&#160;Connection</td></tr></table></div></div>
 
         <hr/>
 

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Session.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Session.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Session.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Session.html Tue Mar 11 22:52:42 2014
@@ -157,7 +157,7 @@
         direct://amq.direct//&lt;queue name&gt;?routingkey=&#8217;&lt;queue name&gt;&#8217;&amp;durable=&#8217;true&#8217;. </p><p>Calling Session#createQueue() has no effect on the Broker.</p><p>Reiterating the advice from the JMS javadoc, it is suggested that this method is not
         generally used. Instead, application should lookup Destinations declared within JNDI.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="JMS-Client-0-8-Client-Understanding-Session-CreateTopic"></a>5.4.4.&#160;CreateTopic</h3></div></div></div><p>In the Qpid JMS client, <a class="ulink" href="http://docs.oracle.com/javaee/6/api/javax/jms/Session.html#createTopic(java.lang.String)" target="_top">Session#createTopic()</a> accepts either a topic name, or a Binding URL. If only name
         is specified the destination will be resolved into binding URL: topic://amq.topic//&lt;topic
-        name&gt;?routingkey=&#8217;&lt;topic name&gt;&#8217;.</p><p>Calling Session#createTopix() has no effect on the Broker.</p><p>Reiterating the advice from the JMS javadoc, it is suggested that this method is not
+        name&gt;?routingkey=&#8217;&lt;topic name&gt;&#8217;.</p><p>Calling Session#createTopic() has no effect on the Broker.</p><p>Reiterating the advice from the JMS javadoc, it is suggested that this method is not
         generally used. Instead, application should lookup Destinations declared within JNDI.</p></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Client-Understanding-Connection.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Client-Understanding.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-MessageProducer.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">5.3.&#160;Connection&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.5.&#160;MessageProducer</td></tr></table></div></div>
 
         <hr/>

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding.html Tue Mar 11 22:52:42 2014
@@ -113,7 +113,7 @@
       documentation assumes the reader has familiarity with these resources.</p><p>The remainder of this section describes how the Qpid JMS client behaves and the effect(s)
       making JMS method calls will have on the Broker. </p><p>There areas where the Qpid JMS client provides features beyond those required for JMS
       compliance. These are described in the sections that follow.</p><p>These sections are also used to bring out differences that may surprise those moving from
-      JMS implementations provided by other vendors.</p><div class="figure"><a id="idp4383760"></a><p class="title"><strong>Figure&#160;5.1.&#160;Architecture of a typical JMS application</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Architecture of a typical JMS application" src="images/QpidJmsOverview.png" /></div></div></div><br class="figure-break" /></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Examples-PubSub.html">Prev</a>&#160;</td><td align="center" width="20%">&#160;</td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-ConnectionFactory.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">4.2.&#160;Publish/subscribe example&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.2.&#160;
 ConnectionFactory</td></tr></table></div></div>
+      JMS implementations provided by other vendors.</p><div class="figure"><a id="idp1069888"></a><p class="title"><strong>Figure&#160;5.1.&#160;Architecture of a typical JMS application</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Architecture of a typical JMS application" src="images/QpidJmsOverview.png" /></div></div></div><br class="figure-break" /></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Examples-PubSub.html">Prev</a>&#160;</td><td align="center" width="20%">&#160;</td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding-ConnectionFactory.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">4.2.&#160;Publish/subscribe example&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;5.2.&#160;
 ConnectionFactory</td></tr></table></div></div>
 
         <hr/>
 

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Connection-URL.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Connection-URL.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Connection-URL.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Connection-URL.html Tue Mar 11 22:52:42 2014
@@ -151,13 +151,13 @@
 						<p> Introduced in version 0.22. </p>
 					</td></tr></tbody></table></div></div><br class="table-break" /><p> Broker lists are specified using a URL in this format: </p><pre class="programlisting">brokerlist=&lt;transport&gt;://&lt;host&gt;[:&lt;;port&gt;](?&lt;param&gt;='&lt;value&gt;')(&amp;&lt;param&gt;='&lt;value&gt;')*</pre><p> For instance, this is a typical broker list: </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.
-		</p><div class="example"><a id="idp3122480"></a><p class="title"><strong>Example&#160;7.1.&#160;Broker Lists</strong></p><div class="example-contents"><p>A broker list can specify properties to be used when connecting to the broker. This
+		</p><div class="example"><a id="idp6223200"></a><p class="title"><strong>Example&#160;7.1.&#160;Broker Lists</strong></p><div class="example-contents"><p>A broker list can specify properties to be used when connecting to the broker. This
 			broker list specifies options for configuring heartbeating</p><pre class="programlisting">amqp://guest:guest@test/test?brokerlist='tcp://ip1:5672?heartbeat='5''</pre><p>This broker list specifies some SSL options</p><pre class="programlisting">amqp://guest:guest@test/test?brokerlist='tcp://ip1:5672?ssl='true'&amp;ssl_cert_alias='cert1''</pre><p> This broker list specifies two brokers using the connectdelay and retries broker
 			options. It also illustrates the failover connection URL property. </p><pre class="programlisting">amqp://guest:guest@/test?failover='roundrobin?cyclecount='2''
 	  &amp;brokerlist='tcp://ip1:5672?retries='5'&amp;connectdelay='2000';tcp://ip2:5672?retries='5'&amp;connectdelay='2000''
 	  </pre></div></div><br class="example-break" /><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Broker option quoting</h3><p>Take care with the quoting surrounding broker option values. Each broker option value
 				<span class="emphasis"><em>must</em></span> be surrounded with their own single quotes ('). This is in
-			addition to the quotes surround the connection option value.</p></div><p>The following broker list options are supported.</p><div class="table"><a id="idp4404784"></a><p class="title"><strong>Table&#160;7.2.&#160;Broker List Options</strong></p><div class="table-contents"><table border="1" summary="Broker List Options" width="100%"><colgroup><col /><col /><col /></colgroup><thead><tr><th> Option </th><th> Type </th><th> Description </th></tr></thead><tbody><tr><td><a id="JMS-Client-0-8-Connection-URL-BrokerOptions-Heartbeat"></a> heartbeat </td><td> Long </td><td> Frequency of heartbeat messages (in seconds). A value of 0 disables
+			addition to the quotes surround the connection option value.</p></div><p>The following broker list options are supported.</p><div class="table"><a id="idp6230528"></a><p class="title"><strong>Table&#160;7.2.&#160;Broker List Options</strong></p><div class="table-contents"><table border="1" summary="Broker List Options" width="100%"><colgroup><col /><col /><col /></colgroup><thead><tr><th> Option </th><th> Type </th><th> Description </th></tr></thead><tbody><tr><td><a id="JMS-Client-0-8-Connection-URL-BrokerOptions-Heartbeat"></a> heartbeat </td><td> Long </td><td> Frequency of heartbeat messages (in seconds). A value of 0 disables
 						heartbeating. <p>For compatibility with old client configuration, option
 								<code class="varname">idle_timeout</code> (in milliseconds) is also
 							supported.</p>

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples-PubSub.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples-PubSub.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples-PubSub.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples-PubSub.html Tue Mar 11 22:52:42 2014
@@ -169,7 +169,7 @@ public class StocksExample {
 						<code class="literal">sub2</code>. Durable subscriptions retain messages for the
 					client even when the client is disconnected, until the subscription is
 					unsubscribed. Subscription 2 has a (commented out) message selector argument so
-					you can conveniently experiement with the effect of those. <a class="footnote" href="#ftn.idp3084768" id="idp3084768"><sup class="footnote">[2]</sup></a></p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-pubsub-unsubscribe"></a><a href="#pubsub-java-unsubscribe">(3)</a> </p></td><td align="left" valign="top"><p>Unsubscribes the two durable subscribers, permanently removing the knowledge
+					you can conveniently experiement with the effect of those. <a class="footnote" href="#ftn.idp3312112" id="idp3312112"><sup class="footnote">[2]</sup></a></p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-pubsub-unsubscribe"></a><a href="#pubsub-java-unsubscribe">(3)</a> </p></td><td align="left" valign="top"><p>Unsubscribes the two durable subscribers, permanently removing the knowledge
 					of the subscriptions from the system. An application would normally
 						<span class="emphasis"><em>NOT</em></span> do this. The typical use-case for durable
 					subsciption is one where the subscription exists over an extended period of
@@ -178,7 +178,7 @@ java.naming.factory.initial = org.apache
 connectionfactory.qpidConnectionFactory = amqp://guest:guest@clientid/?brokerlist='tcp://localhost:5672'
 topic.myprices = prices <a class="co" href="JMS-Client-0-8-Examples-PubSub.html#callout-pubsub-properties-destination" id="pubsub-properties-destination">(1)</a>
 	</pre></div></div><br class="example-break" /><div class="calloutlist"><table border="0" summary="Callout list"><tr><td align="left" valign="top" width="5%"><p><a id="callout-pubsub-properties-destination"></a><a href="#pubsub-properties-destination">(1)</a> </p></td><td align="left" valign="top"><p>Defines a topic for which MessageProducers and/or MessageConsumers send and
-					receive messages. The format of this entry is described in <a class="xref" href="JMS-Client-0-8-JNDI-Properties-Format-Topic.html" title="6.3.&#160;Topic">Section&#160;6.3, &#8220;Topic&#8221;</a>.</p></td></tr></table></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp3084768"><p><a class="para" href="#idp3084768"><sup class="para">[2] </sup></a>Each durable subscription is implemented as a queue on the Broker. See
+					receive messages. The format of this entry is described in <a class="xref" href="JMS-Client-0-8-JNDI-Properties-Format-Topic.html" title="6.3.&#160;Topic">Section&#160;6.3, &#8220;Topic&#8221;</a>.</p></td></tr></table></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp3312112"><p><a class="para" href="#idp3312112"><sup class="para">[2] </sup></a>Each durable subscription is implemented as a queue on the Broker. See
 								<a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageConsumer.html#JMS-Client-0-8-Client-Understanding-MessageConsumer-TopicSubscriptions" title="5.6.2.&#160;Topic Subscriptions">Section&#160;5.6.2, &#8220;Topic Subscriptions&#8221;</a> for details.</p></div></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Examples.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Examples.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Client-Understanding.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter&#160;4.&#160;Examples&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;Chapter&#160;5.&#160;Understanding the Qpid JMS client</td></tr></table></div></div>
 
         <hr/>

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples.html Tue Mar 11 22:52:42 2014
@@ -164,7 +164,7 @@ public class Hello {
 	</pre></div></div><br class="example-break" /><div class="calloutlist"><table border="0" summary="Callout list"><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-properties"></a><a href="#ptp-java-properties">(1)</a> </p></td><td align="left" valign="top"><p>Loads the JNDI properties file, which specifies the connection factory, queues
 					and topics. See <a class="xref" href="JMS-Client-0-8-JNDI-Properties-Format.html" title="Chapter&#160;6.&#160;JNDI Properties Format">Chapter&#160;6, <em>JNDI Properties Format</em></a> for
 					details.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-context"></a><a href="#ptp-java-context">(2)</a> </p></td><td align="left" valign="top"><p>Creates the JNDI initial context.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-connection-factory"></a><a href="#ptp-java-connection-factory">(3)</a> </p></td><td align="left" valign="top"><p>Looks up a JMS connection factory for Qpid.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-connection"></a><a href="#ptp-java-connection">(4)</a> </p></td><td align="left" valign="top"><p>Creates a JMS connection. Creating the JMS connections establishes the
-					connection to the Broker.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-start"></a><a href="#ptp-java-start">(5)</a> </p></td><td align="left" valign="top"><p>Starts the connection, required for the consumption of messages.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-session"></a><a href="#ptp-java-session">(6)</a> </p></td><td align="left" valign="top"><p>Creates a transactional session.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-destination"></a><a href="#ptp-java-destination">(7)</a> </p></td><td align="left" valign="top"><p>Looks up a destination for the queue with JNDI name <span class="emphasis"><em>myqueue</em></span>.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-consumer"></a><a href="#ptp-java-consumer">(8)</a> </p></td><td align="left" valign="top"><p>Creates a consumer that reads messages from the queue<a class="footnote" href=
 "#ftn.idp3214448" id="idp3214448"><sup class="footnote">[1]</sup></a>.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-producer"></a><a href="#ptp-java-producer">(9)</a> </p></td><td align="left" valign="top"><p>Creates a producer that sends messages to the queue.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-send"></a><a href="#ptp-java-send">(10)</a> </p></td><td align="left" valign="top"><p>Creates a new message of type <span class="emphasis"><em>javax.jms.TextMessage</em></span>, publishes the message and commits the
+					connection to the Broker.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-start"></a><a href="#ptp-java-start">(5)</a> </p></td><td align="left" valign="top"><p>Starts the connection, required for the consumption of messages.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-session"></a><a href="#ptp-java-session">(6)</a> </p></td><td align="left" valign="top"><p>Creates a transactional session.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-destination"></a><a href="#ptp-java-destination">(7)</a> </p></td><td align="left" valign="top"><p>Looks up a destination for the queue with JNDI name <span class="emphasis"><em>myqueue</em></span>.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-consumer"></a><a href="#ptp-java-consumer">(8)</a> </p></td><td align="left" valign="top"><p>Creates a consumer that reads messages from the queue<a class="footnote" href=
 "#ftn.idp3229264" id="idp3229264"><sup class="footnote">[1]</sup></a>.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-producer"></a><a href="#ptp-java-producer">(9)</a> </p></td><td align="left" valign="top"><p>Creates a producer that sends messages to the queue.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-send"></a><a href="#ptp-java-send">(10)</a> </p></td><td align="left" valign="top"><p>Creates a new message of type <span class="emphasis"><em>javax.jms.TextMessage</em></span>, publishes the message and commits the
 					session.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-receive"></a><a href="#ptp-java-receive">(11)</a> </p></td><td align="left" valign="top"><p>Reads the next available message (awaiting indefinitely if necessary) and
 					commits the session.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-close"></a><a href="#ptp-java-close">(12)</a> </p></td><td align="left" valign="top"><p>Closes the Connection. All sessions owned by the Connection along with their
 					MessageConsumers and MessageProducers are automatically closed. The connection
@@ -175,7 +175,7 @@ connectionfactory.qpidConnectionFactory 
 queue.myqueue = queue1                                                                                   <a class="co" href="JMS-Client-0-8-Examples.html#callout-ptp-properties-destination" id="ptp-properties-destination">(2)</a>
 	</pre></div></div><br class="example-break" /><div class="calloutlist"><table border="0" summary="Callout list"><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-properties-connectionfactory"></a><a href="#ptp-properties-connectionfactory">(1)</a> </p></td><td align="left" valign="top"><p>Defines a connection factory from which Connections can be created. The syntax
 					of a ConnectionURL is given in <a class="xref" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Chapter&#160;7, <em>Connection URLs</em></a>.</p></td></tr><tr><td align="left" valign="top" width="5%"><p><a id="callout-ptp-properties-destination"></a><a href="#ptp-properties-destination">(2)</a> </p></td><td align="left" valign="top"><p>Defines a queue for which MessageProducers and/or MessageConsumers send and
-					receive messages. The format of these entries is described in <a class="xref" href="JMS-Client-0-8-JNDI-Properties-Format-Queue.html" title="6.2.&#160;Queue">Section&#160;6.2, &#8220;Queue&#8221;</a>.</p></td></tr></table></div></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp3214448"><p><a class="para" href="#idp3214448"><sup class="para">[1] </sup></a>Creating consumer will automatically create the queue on the Broker
+					receive messages. The format of these entries is described in <a class="xref" href="JMS-Client-0-8-JNDI-Properties-Format-Queue.html" title="6.2.&#160;Queue">Section&#160;6.2, &#8220;Queue&#8221;</a>.</p></td></tr></table></div></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp3229264"><p><a class="para" href="#idp3229264"><sup class="para">[1] </sup></a>Creating consumer will automatically create the queue on the Broker
 							and bind it to an exchange. Specifically, in this case as the
 								<code class="literal">queue.</code> form is used in the JNDI properties the
 							effect will be to create a queue called <code class="literal">queue1</code> on the

Modified: qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html (original)
+++ qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html Tue Mar 11 22:52:42 2014
@@ -110,7 +110,7 @@
         <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&#160;9.&#160;System Properties</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="JMS-Client-0-8-Binding-URL.html">Prev</a>&#160;</td><th align="center" width="60%">&#160;</th><td align="right" width="20%">&#160;<a accesskey="n" href="JMS-Client-0-8-Logging.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="JMS-Client-0-8-System-Properties"></a>Chapter&#160;9.&#160;System Properties</h1></div></div></div><p>The following system properties affect the behaviour of the Qpid JMS client. System
 		properties are global in nature so affect all Qpid interactions made from within the same
 		JVM. For many options, there are equivalent <a class="link" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a> options allowing the option to be controlled at the level of the
-		Connection.</p><div class="table"><a id="idp5730624"></a><p class="title"><strong>Table&#160;9.1.&#160;System Properties Affecting Connection Behaviour</strong></p><div class="table-contents"><table border="1" summary="System Properties Affecting Connection Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.amqp.version</td><td>string</td><td>0-10</td><td><p>Sets the AMQP version to be used - currently supports one of
+		Connection.</p><div class="table"><a id="idp3175696"></a><p class="title"><strong>Table&#160;9.1.&#160;System Properties Affecting Connection Behaviour</strong></p><div class="table-contents"><table border="1" summary="System Properties Affecting Connection Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.amqp.version</td><td>string</td><td>0-10</td><td><p>Sets the AMQP version to be used - currently supports one of
 							{0-8,0-9,0-91,0-10}.</p><p>The client will begin negotiation at
 							the specified version and only negotiate downwards if the Broker does
 							not support the specified version.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-Heartbeat"></a>qpid.heartbeat</td><td>int</td><td><p>Defaults to the heartbeat value suggested by the Broker, if
@@ -122,7 +122,7 @@
 								<code class="varname">amqj.heartbeat.delay</code> is supported.</p></td></tr><tr><td>ignore_setclientID</td><td>boolean</td><td>false</td><td>If a client ID is specified in the connection URL it's used or else an ID
 						is generated. If an ID is specified after it's been set Qpid will throw an
 						exception. <p>Setting this property to 'true' will disable that check and
-							allow you to set a client ID of your choice later on.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp1618064"></a><p class="title"><strong>Table&#160;9.2.&#160;Config Options For Session Behaviour</strong></p><div class="table-contents"><table border="1" summary="Config Options For Session Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td><a id="JMS-Client-0-8-System-Properties-DestSyntax"></a>qpid.dest_syntax</td><td>String</td><td>ADDR</td><td><p>The default addressing syntax.  The Address (ADDR) syntax is supported when using AMQP 0-10.  Binding URL (BURL)
+							allow you to set a client ID of your choice later on.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp3372672"></a><p class="title"><strong>Table&#160;9.2.&#160;Config Options For Session Behaviour</strong></p><div class="table-contents"><table border="1" summary="Config Options For Session Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td><a id="JMS-Client-0-8-System-Properties-DestSyntax"></a>qpid.dest_syntax</td><td>String</td><td>ADDR</td><td><p>The default addressing syntax.  The Address (ADDR) syntax is supported when using AMQP 0-10.  Binding URL (BURL)
 					  is supported by AMQP protocols 0-8 through to 0-10.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-Maxprefetch"></a>max_prefetch</td><td>int</td><td>500</td><td><p>Maximum number of pre-fetched messages per Session. This can also
 							be defaulted for sessions created on a particular connection using the
 								<a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-ConnectionOptions-Maxprefetch">Connection URL</a> options.</p></td></tr><tr><td>qpid.use_legacy_map_message</td><td>boolean</td><td>false</td><td><p>If set will use the old map message encoding. By default the Map
@@ -130,7 +130,7 @@
 							also be set per connection using the <a class="link" href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-ConnectionOptions-UseLegacyMap">Connection URL</a> options.</p></td></tr><tr><td>qpid.jms.daemon.dispatcher</td><td>boolean</td><td>false</td><td><p>Controls whether the Session dispatcher thread is a daemon thread
 							or not. If this system property is set to true then the Session
 							dispatcher threads will be created as daemon threads. This setting is
-							introduced in version 0.16.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp4797440"></a><p class="title"><strong>Table&#160;9.3.&#160;Config Options For Consumer Behaviour</strong></p><div class="table-contents"><table border="1" summary="Config Options For Consumer Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td><a id="JMS-Client-0-8-System-Properties-DeclareExchanges"></a>qpid.declare_exchanges</td><td>Boolean</td><td>true</td><td><p>If true, creating a consumer will also declare the exchange on the
+							introduced in version 0.16.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6266544"></a><p class="title"><strong>Table&#160;9.3.&#160;Config Options For Consumer Behaviour</strong></p><div class="table-contents"><table border="1" summary="Config Options For Consumer Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td><a id="JMS-Client-0-8-System-Properties-DeclareExchanges"></a>qpid.declare_exchanges</td><td>Boolean</td><td>true</td><td><p>If true, creating a consumer will also declare the exchange on the
 							Broker (specified within the Binding URL associated with the
 							Destination), creating it if is does not already exist.
 						</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-DeclareQueues"></a>qpid.declare_queues</td><td>Boolean</td><td>true</td><td><p>If true, creating a consumer will also declare the queue on the
@@ -139,7 +139,7 @@
 						exist.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-BindQueues"></a>qpid.bind_queues</td><td>Boolean</td><td>true</td><td><p>If true, creating a consumer will also bind the queue to the
 							to the exchange using the routing key as a binding key. The
 							exchange name, queue name and routing key are taken from 
-							the Binding URL associated with the Destination.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-RejectBehaviour"></a>qpid.reject.behaviour</td><td>String</td><td>NORMAL</td><td><p>Used with the maximum delivery count feature. See <a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageConsumer.html#JMS-Client-0-8-Client-Understanding-MessageConsumer-MaximumDeliveryCount" title="5.6.3.&#160;Maximum Delivery Count">Section&#160;5.6.3, &#8220;Maximum Delivery Count&#8221;</a> for details.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp1278704"></a><p class="title"><strong>Table&#160;9.4.&#160;Config Options For Producer Behaviour</strong></p><div class="table-contents"><table border="1" summary="Config Options For Producer Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td
 ><a id="JMS-Client-0-8-System-Properties-DefaultMandatory"></a>qpid.default_mandatory</td><td>Boolean</td><td>True</td><td><p>If true, messages sent to Queue destinations for which cannot be
+							the Binding URL associated with the Destination.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-RejectBehaviour"></a>qpid.reject.behaviour</td><td>String</td><td>NORMAL</td><td><p>Used with the maximum delivery count feature. See <a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageConsumer.html#JMS-Client-0-8-Client-Understanding-MessageConsumer-MaximumDeliveryCount" title="5.6.3.&#160;Maximum Delivery Count">Section&#160;5.6.3, &#8220;Maximum Delivery Count&#8221;</a> for details.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6302928"></a><p class="title"><strong>Table&#160;9.4.&#160;Config Options For Producer Behaviour</strong></p><div class="table-contents"><table border="1" summary="Config Options For Producer Behaviour" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td
 ><a id="JMS-Client-0-8-System-Properties-DefaultMandatory"></a>qpid.default_mandatory</td><td>Boolean</td><td>True</td><td><p>If true, messages sent to Queue destinations for which cannot be
 							routed to at least one queue on the Broker, will be returned to the
 							application. See <a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageProducer.html#JMS-Client-0-8-Client-Understanding-MessageProducer-MandatoryMessage" title="5.5.1.&#160;Mandatory Messages">Section&#160;5.5.1, &#8220;Mandatory Messages&#8221;</a> for more details.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-DefaultMandatoryTopic"></a>qpid.default_mandatory_topic</td><td>Boolean</td><td>False</td><td><p>If true, messages sent to Topic destinations for which cannot be
 							routed to at least one queue on the Broker, will be returned to the
@@ -147,10 +147,10 @@
 							Broker is able to route the message to at least one queue with a
 							consumer attached. See <a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageProducer.html#JMS-Client-0-8-Client-Understanding-MessageProducer-ImmediateMessage" title="5.5.3.&#160;Immediate Messages">Section&#160;5.5.3, &#8220;Immediate Messages&#8221;</a> for more details.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-FlowControlWaitFailure"></a>qpid.flow_control_wait_failure</td><td>Long</td><td>60000</td><td><p>Used with <a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageProducer.html#JMS-Client-0-8-Client-Understanding-MessageProducer-FlowControl" title="5.5.4.&#160;Flow Control">Section&#160;5.5.4, &#8220;Flow Control&#8221;</a>. The amount of time (in milliseconds) to wait before timing
 							out.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-FlowControlWaitNotifyPeriod"></a>qpid.flow_control_wait_notify_period</td><td>Long</td><td>5000</td><td><p>Used with <a class="xref" href="JMS-Client-0-8-Client-Understanding-MessageProducer.html#JMS-Client-0-8-Client-Understanding-MessageProducer-FlowControl" title="5.5.4.&#160;Flow Control">Section&#160;5.5.4, &#8220;Flow Control&#8221;</a>. The frequency at which the log message informing that the producer
-							is flow controlled .</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6197280"></a><p class="title"><strong>Table&#160;9.5.&#160;Config Options For Threading</strong></p><div class="table-contents"><table border="1" summary="Config Options For Threading" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.thread_factory</td><td>string</td><td>org.apache.qpid.thread.DefaultThreadFactory</td><td><p>Specifies the thread factory to use.</p><p>If using a real
+							is flow controlled .</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6324912"></a><p class="title"><strong>Table&#160;9.5.&#160;Config Options For Threading</strong></p><div class="table-contents"><table border="1" summary="Config Options For Threading" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.thread_factory</td><td>string</td><td>org.apache.qpid.thread.DefaultThreadFactory</td><td><p>Specifies the thread factory to use.</p><p>If using a real
 							time JVM, you need to set the above property to
 								<code class="varname">org.apache.qpid.thread.RealtimeThreadFactory</code>.</p></td></tr><tr><td>qpid.rt_thread_priority</td><td>int</td><td>20</td><td><p>Specifies the priority (1-99) for Real time threads created by the
-							real time thread factory.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6207792"></a><p class="title"><strong>Table&#160;9.6.&#160;Config Options For I/O</strong></p><div class="table-contents"><table border="1" summary="Config Options For I/O" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.transport</td><td>string</td><td>org.apache.qpid.transport.network.io.IoNetworkTransport</td><td><p>The transport implementation to be used.</p><p>A user could
+							real time thread factory.</p></td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6335424"></a><p class="title"><strong>Table&#160;9.6.&#160;Config Options For I/O</strong></p><div class="table-contents"><table border="1" summary="Config Options For I/O" width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.transport</td><td>string</td><td>org.apache.qpid.transport.network.io.IoNetworkTransport</td><td><p>The transport implementation to be used.</p><p>A user could
 							specify an alternative transport mechanism that implements the interface
 								<code class="varname">org.apache.qpid.transport.network.OutgoingNetworkTransport</code>.</p></td></tr><tr><td><a id="JMS-Client-0-8-System-Properties-SyncOpTimeout"></a>qpid.sync_op_timeout</td><td>long</td><td>60000</td><td><p>The length of time (in milliseconds) to wait for a synchronous
 							operation to complete.</p><p>For compatibility with older clients,
@@ -177,7 +177,7 @@
 							re-establish the connection. If a reconnection attempt exceeds the
 							timeout, the entire failover process is aborted.</p>
 						<p>It is only applicable for AMQP 0-8/0-9/0-9-1 clients.</p>
-					</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6238448"></a><p class="title"><strong>Table&#160;9.7.&#160;Config Options For Security - Using SSL for securing connections or using EXTERNAL as
+					</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6366400"></a><p class="title"><strong>Table&#160;9.7.&#160;Config Options For Security - Using SSL for securing connections or using EXTERNAL as
 			the SASL mechanism.</strong></p><div class="table-contents"><table border="1" summary="Config Options For Security - Using SSL for securing connections or using EXTERNAL as&#10;			the SASL mechanism." width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>qpid.ssl_timeout</td><td>long</td><td>60000</td><td><p>Timeout value used by the Java SSL engine when waiting on
 							operations.</p></td></tr><tr><td>qpid.ssl.KeyManagerFactory.algorithm</td><td>string</td><td>-</td><td>
 						<p>The key manager factory algorithm name. If not set, defaults to the
@@ -191,13 +191,13 @@
 								<code class="literal">TrustManagerFactory.getDefaultAlgorithm()</code></p>
 						<p>For compatibility with older clients, the synonym
 								<code class="varname">qpid.ssl.trustStoreCertType</code> is supported.</p>
-					</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6254400"></a><p class="title"><strong>Table&#160;9.8.&#160;Config Options For Security - Standard JVM properties needed when Using SSL for
-			securing connections or using EXTERNAL as the SASL mechanism.<a class="footnote" href="#ftn.idp6255376" id="idp6255376"><sup class="footnote">[a]</sup></a></strong></p><div class="table-contents"><table border="1" summary="Config Options For Security - Standard JVM properties needed when Using SSL for&#10;			securing connections or using EXTERNAL as the SASL mechanism.Qpid allows you to have per connection key and trust stores if required. If&#10;					specified per connection, the JVM arguments are ignored." width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>javax.net.ssl.keyStore</td><td>string</td><td>jvm default</td><td><p>Specifies the key store path.</p><p>This can also be set per
+					</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="idp6382512"></a><p class="title"><strong>Table&#160;9.8.&#160;Config Options For Security - Standard JVM properties needed when Using SSL for
+			securing connections or using EXTERNAL as the SASL mechanism.<a class="footnote" href="#ftn.idp6383488" id="idp6383488"><sup class="footnote">[a]</sup></a></strong></p><div class="table-contents"><table border="1" summary="Config Options For Security - Standard JVM properties needed when Using SSL for&#10;			securing connections or using EXTERNAL as the SASL mechanism.Qpid allows you to have per connection key and trust stores if required. If&#10;					specified per connection, the JVM arguments are ignored." width="100%"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Property Name</th><th>Type</th><th>Default Value</th><th>Description</th></tr></thead><tbody><tr><td>javax.net.ssl.keyStore</td><td>string</td><td>jvm default</td><td><p>Specifies the key store path.</p><p>This can also be set per
 							connection using the <a class="link" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a> options.</p></td></tr><tr><td>javax.net.ssl.keyStorePassword</td><td>string</td><td>jvm default</td><td><p>Specifies the key store password.</p><p>This can also be set
 							per connection using the <a class="link" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a> options.</p></td></tr><tr><td>javax.net.ssl.trustStore</td><td>string</td><td>jvm default</td><td><p>Specifies the trust store path.</p><p>This can also be set
 							per connection using the <a class="link" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a> options.</p></td></tr><tr><td>javax.net.ssl.trustStorePassword</td><td>string</td><td>jvm default</td><td><p>Specifies the trust store password.</p><p>This can also be
 							set per connection using the <a class="link" href="JMS-Client-0-8-Connection-URL.html" title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a>
-							options.</p></td></tr></tbody><tbody class="footnotes"><tr><td colspan="4"><div class="footnote" id="ftn.idp6255376"><p><a class="para" href="#idp6255376"><sup class="para">[a] </sup></a>Qpid allows you to have per connection key and trust stores if required. If
+							options.</p></td></tr></tbody><tbody class="footnotes"><tr><td colspan="4"><div class="footnote" id="ftn.idp6383488"><p><a class="para" href="#idp6383488"><sup class="para">[a] </sup></a>Qpid allows you to have per connection key and trust stores if required. If
 					specified per connection, the JVM arguments are ignored.</p></div></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Binding-URL.html">Prev</a>&#160;</td><td align="center" width="20%">&#160;</td><td align="right" width="40%">&#160;<a accesskey="n" href="JMS-Client-0-8-Logging.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter&#160;8.&#160;Binding URL&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;Chapter&#160;10.&#160;Logging</td></tr></table></div></div>
 
         <hr/>



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


Mime
View raw message