Modified: 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html
URL: 
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html
 Sat Jan  2 23:59:48 2016
@@ -114,8 +114,8 @@ https://github.com/apache/qpid-proton/bl
         <ul id="-path-navigation"><li><a 
href="/index.html">Home</a></li><li><a 
href="/releases/index.html">Releases</a></li><li><a 
href="/releases/qpid-java-trunk/index.html">Qpid Java Trunk</a></li><li><a 
href="/releases/qpid-java-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>C.2.&#160;Binding 
Management</li></ul>
 
         <div id="-middle-content">
-          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">C.2.&#160;Binding Management</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html">Prev</a>&#160;</td><th 
align="center" width="60%">Appendix&#160;C.&#160;JMS Extensions</th><td 
align="right" width="20%">&#160;<a accesskey="n" 
href="JMS-Client-0-8-Appendix-PooledConnecytionFactory.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-Appendix-JMS-Extensions-Binding"></a>C.2.&#160;Binding 
Management</h2></div></div></div><p>These extensions allow bindings to be 
created or removed.</p><div class="section"><div 
class="titlepage"><div><div><h3 class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Binding-Creation"></a>C.2.1.&#160;Binding
 creation</h3></div></div></div><p>The following example illustrates the 
 creation of queue binding to topic exchange with
-        JMS client.</p><div class="example"><a id="idm139643151698272"></a><p 
class="title"><strong>Example&#160;C.2.&#160;Binding a queue using 
JMS</strong></p><div class="example-contents"><pre 
class="programlisting">ConnectionFactory connectionFactory = ...
+          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">C.2.&#160;Binding Management</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html">Prev</a>&#160;</td><th 
align="center" width="60%">Appendix&#160;C.&#160;JMS Extensions</th><td 
align="right" width="20%">&#160;<a accesskey="n" 
href="JMS-Client-0-8-Appendix-PooledConnecytionFactory.html">Next</a></td></tr></table><hr
 /></div><div class="section"><div class="titlepage"><div><div><h2 
class="title" style="clear: both"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Binding"></a>C.2.&#160;Binding 
Management</h2></div></div></div><p>These extensions allow bindings to be 
created or removed.</p><div class="section"><div 
class="titlepage"><div><div><h3 class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Binding-Creation"></a>C.2.1.&#160;Binding
 creation</h3></div></div></div><p>The following exam
 ple illustrates the creation of queue binding to topic exchange with
+        JMS client.</p><div class="example"><a id="d0e2908"></a><p 
class="title"><strong>Example&#160;C.2.&#160;Binding a queue using 
JMS</strong></p><div class="example-contents"><pre 
class="programlisting">ConnectionFactory connectionFactory = ...
 Connection connection = connectionFactory.createConnection();
 AMQSession&lt;?, ?&gt; session = 
(AMQSession&lt;?,?&gt;)connection.createSession(false, 
Session.AUTO_ACKNOWLEDGE);
 
@@ -133,7 +133,7 @@ arguments.put("x-filter-jms-selector", "
 
 // create binding
 session.bindQueue(queueName, routingKey, 
FieldTable.convertToFieldTable(arguments),
-    new AMQShortString("amq.topic"), destination);</pre></div></div><br 
class="example-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-Appendix-JMS-Extensions.html">Prev</a>&#160;</td><td 
align="center" width="20%"><a accesskey="u" 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html">Up</a></td><td align="right" 
width="40%">&#160;<a accesskey="n" 
href="JMS-Client-0-8-Appendix-PooledConnecytionFactory.html">Next</a></td></tr><tr><td
 align="left" valign="top" width="40%">Appendix&#160;C.&#160;JMS 
Extensions&#160;</td><td align="center" width="20%"><a accesskey="h" 
href="index.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;Appendix&#160;D.&#160;PooledConnectionFactory</td></tr></table></div></div>
+    new AMQShortString("amq.topic"), destination);</pre></div></div><br 
class="example-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-Appendix-JMS-Extensions.html">Prev</a>&#160;</td><td 
align="center" width="20%"><a accesskey="u" 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html">Up</a></td><td align="right" 
width="40%">&#160;<a accesskey="n" 
href="JMS-Client-0-8-Appendix-PooledConnecytionFactory.html">Next</a></td></tr><tr><td
 align="left" valign="top" width="40%">Appendix&#160;C.&#160;JMS 
Extensions&#160;</td><td align="center" width="20%"><a accesskey="h" 
href="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;Appendix&#160;D.&#160;PooledConnectionFactory</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions.html
URL: 
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-JMS-Extensions.html
 Sat Jan  2 23:59:48 2016
@@ -114,12 +114,12 @@ https://github.com/apache/qpid-proton/bl
         <ul id="-path-navigation"><li><a 
href="/index.html">Home</a></li><li><a 
href="/releases/index.html">Releases</a></li><li><a 
href="/releases/qpid-java-trunk/index.html">Qpid Java Trunk</a></li><li><a 
href="/releases/qpid-java-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>Appendix&#160;C.&#160;JMS 
Extensions</li></ul>
 
         <div id="-middle-content">
-          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">Appendix&#160;C.&#160;JMS Extensions</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Appendix-Maven.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-Appendix-JMS-Extensions-Binding.html">Next</a></td></tr></table><hr
 /></div><div class="appendix"><div class="titlepage"><div><div><h1 
class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions"></a>Appendix&#160;C.&#160;JMS 
Extensions</h1></div></div></div><div class="toc"><p><strong>Table of 
Contents</strong></p><dl class="toc"><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html#JMS-Client-0-8-Appendix-JMS-Extensions-Queue">C.1.
 Queue Management</a></span></dt><dd><dl><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html#JMS-C
 lient-0-8-Appendix-JMS-Extensions-Queue-Creation">C.1.1. Queue 
creation</a></span></dt></dl></dd><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html">C.2. Binding 
Management</a></span></dt><dd><dl><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html#JMS-Client-0-8-Appendix-JMS-Extensions-Binding-Creation">C.2.1.
 Binding creation</a></span></dt></dl></dd></dl></div><p>This section 
illustrates using Qpid specific extentions to JMX for the managament of queues,
+          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">Appendix&#160;C.&#160;JMS Extensions</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Appendix-Maven.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-Appendix-JMS-Extensions-Binding.html">Next</a></td></tr></table><hr
 /></div><div class="appendix"><div class="titlepage"><div><div><h1 
class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions"></a>Appendix&#160;C.&#160;JMS 
Extensions</h1></div></div></div><div class="toc"><p><strong>Table of 
Contents</strong></p><dl class="toc"><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html#JMS-Client-0-8-Appendix-JMS-Extensions-Queue">C.1.
 Queue Management</a></span></dt><dd><dl><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions.html#JMS-C
 lient-0-8-Appendix-JMS-Extensions-Queue-Creation">C.1.1. Queue 
creation</a></span></dt></dl></dd><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html">C.2. Binding 
Management</a></span></dt><dd><dl><dt><span class="section"><a 
href="JMS-Client-0-8-Appendix-JMS-Extensions-Binding.html#JMS-Client-0-8-Appendix-JMS-Extensions-Binding-Creation">C.2.1.
 Binding creation</a></span></dt></dl></dd></dl></div><p>This section 
illustrates using Qpid specific extentions to JMS for the managament of queues,
   exchanges and bindings.</p><div class="important" style="margin-left: 0.5in; 
margin-right: 0.5in;"><h3 class="title">Important</h3><p>It is not recommended 
that these extensions are generally used. These interfaces are
       subject to change and will not be supported in this form for AMQP 1.0. 
Instead, the reader is
-      directed towards the Managment interfaces of the Broker.</p></div><div 
class="section"><div class="titlepage"><div><div><h2 class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Queue"></a>C.1.&#160;Queue 
Management</h2></div></div></div><p>These extensions allow queues to be created 
or removed.</p><div class="section"><div class="titlepage"><div><div><h3 
class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Queue-Creation"></a>C.1.1.&#160;Queue
 creation</h3></div></div></div><p>The following example illustrates the 
creation of the a LVQ queue from a
+      directed towards the Managment interfaces of the Broker.</p></div><div 
class="section"><div class="titlepage"><div><div><h2 class="title" 
style="clear: both"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Queue"></a>C.1.&#160;Queue 
Management</h2></div></div></div><p>These extensions allow queues to be created 
or removed.</p><div class="section"><div class="titlepage"><div><div><h3 
class="title"><a 
id="JMS-Client-0-8-Appendix-JMS-Extensions-Queue-Creation"></a>C.1.1.&#160;Queue
 creation</h3></div></div></div><p>The following example illustrates the 
creation of the a LVQ queue from a
         javax.jms.Session object. Note that this utilises a Qpid specific 
extension to JMS and
-        involves casting the session object back to its Qpid 
base-class.</p><div class="example"><a id="idm139643149573360"></a><p 
class="title"><strong>Example&#160;C.1.&#160;Creation of an LVQ using the Qpid 
extension to JMS</strong></p><div class="example-contents"><pre 
class="programlisting">Map&lt;String,Object&gt; arguments = new 
HashMap&lt;String, Object&gt;();
+        involves casting the session object back to its Qpid 
base-class.</p><div class="example"><a id="d0e2893"></a><p 
class="title"><strong>Example&#160;C.1.&#160;Creation of an LVQ using the Qpid 
extension to JMS</strong></p><div class="example-contents"><pre 
class="programlisting">Map&lt;String,Object&gt; arguments = new 
HashMap&lt;String, Object&gt;();
 arguments.put("qpid.last_value_queue_key","ISIN");
 AMQDestination amqQueue = (AMQDestination) context.lookup("myqueue");
 ((AMQSession&lt;?,?&gt;) session).createQueue(
@@ -128,7 +128,7 @@ AMQDestination amqQueue = (AMQDestinatio
         amqQueue.isDurable(),
         amqQueue.isExclusive(),
         arguments);
-</pre></div></div><br class="example-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-Appendix-Maven.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-Appendix-JMS-Extensions-Binding.html">Next</a></td></tr><tr><td
 align="left" valign="top" width="40%">Appendix&#160;B.&#160;Minimal Maven 
POM&#160;</td><td align="center" width="20%"><a accesskey="h" 
href="index.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;C.2.&#160;Binding Management</td></tr></table></div></div>
+</pre></div></div><br class="example-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-Appendix-Maven.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-Appendix-JMS-Extensions-Binding.html">Next</a></td></tr><tr><td
 align="left" valign="top" width="40%">Appendix&#160;B.&#160;Minimal Maven 
POM&#160;</td><td align="center" width="20%"><a accesskey="h" 
href="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;C.2.&#160;Binding Management</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Maven.html
URL: 
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Maven.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Maven.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Maven.html
 Sat Jan  2 23:59:48 2016
@@ -116,8 +116,8 @@ https://github.com/apache/qpid-proton/bl
         <div id="-middle-content">
           <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">Appendix&#160;B.&#160;Minimal Maven POM</th></tr><tr><td 
align="left" width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Appendix-Exceptions.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-Appendix-JMS-Extensions.html">Next</a></td></tr></table><hr
 /></div><div class="appendix"><div class="titlepage"><div><div><h1 
class="title"><a 
id="JMS-Client-0-8-Appendix-Maven"></a>Appendix&#160;B.&#160;Minimal Maven 
POM</h1></div></div></div><p> The following is a minimal Maven POM required to 
use the Qpid Client. It is suitable for
     use with the <a class="link" href="JMS-Client-0-8-Examples.html" 
title="Chapter&#160;4.&#160;Examples">examples</a> included in this
-    book.</p><div class="example"><a id="idm139643147254128"></a><p 
class="title"><strong>Example&#160;B.1.&#160;Minimal Maven POM 
</strong></p><div class="example-contents"><pre class="programlisting">
-    
+    book.</p><div class="example"><a id="d0e2866"></a><p 
class="title"><strong>Example&#160;B.1.&#160;Minimal Maven POM 
</strong></p><div class="example-contents"><pre class="programlisting">
+
 &lt;project xmlns="http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd"&gt;
   &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
@@ -128,7 +128,7 @@ https://github.com/apache/qpid-proton/bl
     &lt;dependency&gt;
       &lt;groupId&gt;org.apache.qpid&lt;/groupId&gt;
       &lt;artifactId&gt;qpid-client&lt;/artifactId&gt;
-      &lt;version&gt;0.32-SNAPSHOT&lt;/version&gt;
+      &lt;version&gt;6.1.0-SNAPSHOT&lt;/version&gt;
     &lt;/dependency&gt;
     &lt;dependency&gt;
       &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
@@ -142,10 +142,10 @@ https://github.com/apache/qpid-proton/bl
     &lt;/dependency&gt;
   &lt;/dependencies&gt;
 &lt;/project&gt;
-    
+
   </pre></div></div><br class="example-break" /><p>Note: We use the SLF4J 
Binding for Log4J12 here, but any SLF4J Binding could be used
     instead. Similarly, Geronimo JMS Spec is used, but any dependency that 
provides the JMS 1.1
-    specification could be subsituted.</p></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-Appendix-Exceptions.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-Appendix-JMS-Extensions.html">Next</a></td></tr><tr><td 
align="left" valign="top" 
width="40%">Appendix&#160;A.&#160;Exceptions&#160;</td><td align="center" 
width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" 
valign="top" width="40%">&#160;Appendix&#160;C.&#160;JMS 
Extensions</td></tr></table></div></div>
+    specification could be substituted.</p></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-Appendix-Exceptions.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-Appendix-JMS-Extensions.html">Next</a></td></tr><tr><td 
align="left" valign="top" 
width="40%">Appendix&#160;A.&#160;Exceptions&#160;</td><td align="center" 
width="20%"><a accesskey="h" href="JMS-Client-Book.html">Home</a></td><td 
align="right" valign="top" width="40%">&#160;Appendix&#160;C.&#160;JMS 
Extensions</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-PooledConnecytionFactory.html
URL: 
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-PooledConnecytionFactory.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-PooledConnecytionFactory.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-PooledConnecytionFactory.html
 Sat Jan  2 23:59:48 2016
@@ -115,14 +115,14 @@ https://github.com/apache/qpid-proton/bl
 
         <div id="-middle-content">
           <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">Appendix&#160;D.&#160;PooledConnectionFactory</th></tr><tr><td 
align="left" width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Appendix-JMS-Extensions-Binding.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-Appendix-Tomcat-JNDI-Integration.html">Next</a></td></tr></table><hr
 /></div><div class="appendix"><div class="titlepage"><div><div><h1 
class="title"><a 
id="JMS-Client-0-8-Appendix-PooledConnecytionFactory"></a>Appendix&#160;D.&#160;PooledConnectionFactory</h1></div></div></div><p>Qpid
 client provides <code class="literal">PooledConnectionFactory</code> which is 
a special
-    implementation of <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/ConnectionFactory.html"; 
target="_top">ConnectionFactory</a> supporting <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html"; 
target="_top">Connection</a> pooling. </p><p> The <code 
class="literal">PooledConnectionFactory</code> caches a predefined number of 
connections
+    implementation of <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/ConnectionFactory.html"; 
target="_top">ConnectionFactory</a> supporting <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html"; 
target="_top">Connection</a> pooling. </p><p> The <code 
class="literal">PooledConnectionFactory</code> caches a predefined number of 
connections
     thus saving an application which connects frequently time. The <code 
class="literal">Connection</code>
     instance is taken from the pool whenever method
       <code class="literal">PooledConnectionFactory#createConnection()</code> 
is invoked and returned into the
     pool when method <code class="literal">Connection#close()</code> is 
called.</p><p>A user can configure a maximum allowed number of connections to 
remain in pool (10 by
     default) by calling <code 
class="literal">PooledConnectionFactory#setMaxPoolSize(int)</code>. When number
     of connections exceeds the value set for maximum pool size,
-      <code class="literal">PooledConnectionFactory</code> starts to work as a 
normal <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/ConnectionFactory.html"; 
target="_top">ConnectionFactory</a> and creates
+      <code class="literal">PooledConnectionFactory</code> starts to work as a 
normal <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/ConnectionFactory.html"; 
target="_top">ConnectionFactory</a> and creates
     a new connection every time method <code 
class="literal">PooledConnectionFactory#createConnection()</code>
     is invoked.</p><p>The <a class="link" 
href="JMS-Client-0-8-Connection-URL.html" 
title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a> is set by 
invoking
     method <code 
class="literal">PooledConnectionFactory#setConnectionURLString(String)</code>.</p><p>A
 user can specify the maximum time a connection may remain idle in pool by 
calling
@@ -130,7 +130,7 @@ https://github.com/apache/qpid-proton/bl
     milliseconds. If connection is not used within the specified interval it 
is closed
     automatically. </p><p>This implementation can be useful in <span 
class="emphasis"><em>Spring JMS</em></span> based applications. An
     example below demonstrates how to configure <code 
class="literal">PooledConnectionFactory</code> in the
-    Spring xml configuration. </p><div class="example"><a 
id="idm139643151715200"></a><p 
class="title"><strong>Example&#160;D.1.&#160;Example of configuring <span 
class="emphasis"><em>PooledConnectionFactory</em></span> in spring xml
+    Spring xml configuration. </p><div class="example"><a id="d0e2977"></a><p 
class="title"><strong>Example&#160;D.1.&#160;Example of configuring <span 
class="emphasis"><em>PooledConnectionFactory</em></span> in spring xml
         configuration.</strong></p><div class="example-contents"><pre 
class="programlisting">
 &lt;bean id="pooledConnectionFactory" 
class="org.apache.qpid.client.PooledConnectionFactory"&gt;
   &lt;!-- set maximum number of pool connections to 20--&gt;
@@ -138,13 +138,13 @@ https://github.com/apache/qpid-proton/bl
   &lt;!-- set the timeout for connection to remain open in pool without being 
used --&gt;
   &lt;property name="connectionTimeout" value="60000"&gt;&lt;/property&gt;
   &lt;!-- set connection URL as String --&gt;
-  &lt;property name="connectionURLString" 
value="amqp://guest:guest@clientid/default?brokerlist='tcp://localhost:5672?retries='300'&amp;amp;failover='nofailover''&amp;amp;maxprefetch='0'"&gt;&lt;/property&gt;
+  &lt;property name="connectionURLString" 
value="amqp://guest:guest@clientid/default?brokerlist='tcp://localhost:5672?retries='300'&amp;failover='nofailover''&amp;maxprefetch='0'"&gt;&lt;/property&gt;
 &lt;/bean&gt;</pre></div></div><p><br class="example-break" />
   </p><p>
     <span class="emphasis"><em>PooledConnectionFactory</em></span> spring bean 
can be configured with such
       <span class="emphasis"><em>spring-jms</em></span> beans like
       <span class="emphasis"><em>DefaultMessageListenerContainer</em></span> 
and <span class="emphasis"><em>JmsTemplate</em></span>. The
-    example below demonstrates how to do that </p><div class="example"><a 
id="idm139643149807072"></a><p 
class="title"><strong>Example&#160;D.2.&#160;Examples of configuring <span 
class="emphasis"><em>PooledConnectionFactory</em></span> with
+    example below demonstrates how to do that </p><div class="example"><a 
id="d0e3000"></a><p class="title"><strong>Example&#160;D.2.&#160;Examples of 
configuring <span class="emphasis"><em>PooledConnectionFactory</em></span> with
           <span 
class="emphasis"><em>DefaultMessageListenerContainer</em></span> and
         <span class="emphasis"><em>JmsTemplate</em></span>.</strong></p><div 
class="example-contents"><pre class="programlisting">
 &lt;bean id="jmsProducerTemplate" 
class="org.springframework.jms.core.JmsTemplate"&gt;
@@ -165,7 +165,7 @@ https://github.com/apache/qpid-proton/bl
       on <code class="literal">PooledConnectionFactory</code> bean. If this is 
not the case, once the number
       of in-use connections reaches the the <span 
class="emphasis"><em>PooledConnectionFactory#maxPoolSize</em></span>
       a new connection will be opened for each and every message receipt i.e. 
a connection per
-      message anti-pattern.</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-Appendix-JMS-Extensions-Binding.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-Appendix-Tomcat-JNDI-Integration.html">Next</a></td></tr><tr><td
 align="left" valign="top" width="40%">C.2.&#160;Binding 
Management&#160;</td><td align="center" width="20%"><a accesskey="h" 
href="index.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;Appendix&#160;E.&#160;How to bind Qpid destinations and 
connection factories into Tomcat JNDI</td></tr></table></div></div>
+      message anti-pattern.</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-Appendix-JMS-Extensions-Binding.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-Appendix-Tomcat-JNDI-Integration.html">Next</a></td></tr><tr><td
 align="left" valign="top" width="40%">C.2.&#160;Binding 
Management&#160;</td><td align="center" width="20%"><a accesskey="h" 
href="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;Appendix&#160;E.&#160;How to bind Qpid destinations and 
connection factories into Tomcat JNDI</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Tomcat-JNDI-Integration.html
URL: 
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Tomcat-JNDI-Integration.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Tomcat-JNDI-Integration.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Tomcat-JNDI-Integration.html
 Sat Jan  2 23:59:48 2016
@@ -118,52 +118,52 @@ https://github.com/apache/qpid-proton/bl
       Qpid client destinations and connection factories can be registered in 
external JNDI containers, for example, Tomcat JNDI implementation.
   </p><p>
     <code class="literal">org.apache.qpid.jndi.ObjectFactory</code> implements
-    <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/spi/ObjectFactory.html";
 target="_top">javax.naming.spi.ObjectFactory</a>
+    <a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/spi/ObjectFactory.html";
 target="_top">javax.naming.spi.ObjectFactory</a>
     allowing it to create instances of <code 
class="literal">AMQConnectionFactory</code>, <code 
class="literal">PooledConnectionFactory</code>,
     <code class="literal">AMQConnection</code>, <code 
class="literal">AMQQueue</code> and <code class="literal">AMQTopic</code> in 
external JNDI container from
-    <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Reference.html"; 
target="_top">javax.naming.Reference</a>s.
+    <a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Reference.html"; 
target="_top">javax.naming.Reference</a>s.
   </p><p>Additionally,
     <code class="literal">AMQConnectionFactory</code>, <code 
class="literal">PooledConnectionFactory</code> and <code 
class="literal">AMQDestination</code> (parent of
     <code class="literal">AMQQueue</code> and <code 
class="literal">AMQTopic</code>) implement
-    <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Referenceable.html"; 
target="_top">javax.naming.Referenceable</a>
-    allowing creation of <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Reference.html"; 
target="_top">javax.naming.Reference</a> objects
+    <a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Referenceable.html"; 
target="_top">javax.naming.Referenceable</a>
+    allowing creation of <a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Reference.html"; 
target="_top">javax.naming.Reference</a> objects
     for binding in external JNDI implementations.
   </p><p>
     <code class="literal">org.apache.qpid.jndi.ObjectFactory</code> allows the 
creation of:
-    </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li 
class="listitem"><p>
+    </p><div class="itemizedlist"><ul class="itemizedlist" 
style="list-style-type: disc; "><li class="listitem"><p>
           an instance of <code class="literal">ConnectionFactory</code> from a 
<code class="literal">Reference</code> containing reference
-          address (<a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
+          address (<a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
           <code class="literal">connectionURL</code> with content set to a
           <a class="link" href="JMS-Client-0-8-Connection-URL.html" 
title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a>.
         </p></li><li class="listitem"><p>
           an instance of <code class="literal">PooledConnectionFactory</code> 
from a <code class="literal">Reference</code> containing reference
-          address (<a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
+          address (<a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
           <code class="literal">connectionURL</code> with content set to a
           <a class="link" href="JMS-Client-0-8-Connection-URL.html" 
title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a>.
         </p></li><li class="listitem"><p>
           an instance of <code class="literal">AMQConnection</code> from a 
<code class="literal">Reference</code> containing reference
-          address (<a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
+          address (<a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
           <code class="literal">connectionURL</code> with content set to a
           <a class="link" href="JMS-Client-0-8-Connection-URL.html" 
title="Chapter&#160;7.&#160;Connection URLs">Connection URL</a>.
         </p></li><li class="listitem"><p>
           an instance of <code class="literal">AMQQueue</code> from a <code 
class="literal">Reference</code> containing reference
-          address (<a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
-          <code class="literal">address</code> with content set to either <a 
class="ulink" href="../../Programming-In-Apache-Qpid/html/" 
target="_top">Address</a> or
+          address (<a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
+          <code class="literal">address</code> with content set to either <a 
class="link" href="/releases/qpid-0.32/programming/book/" 
target="_top">Address</a> or
           <a class="link" href="JMS-Client-0-8-Binding-URL.html" 
title="Chapter&#160;8.&#160;Binding URL">Binding URL</a>.
         </p></li><li class="listitem"><p>
           an instance of <code class="literal">AMQTopic</code> from a <code 
class="literal">Reference</code> containing reference
-          address (<a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
-          <code class="literal">address</code> with content set to either <a 
class="ulink" href="../../Programming-In-Apache-Qpid/html/" 
target="_top">Address</a> or
+          address (<a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/RefAddr.html"; 
target="_top">javax.naming.RefAddr</a>)
+          <code class="literal">address</code> with content set to either <a 
class="link" href="/releases/qpid-0.32/programming/book/" 
target="_top">Address</a> or
           <a class="link" href="JMS-Client-0-8-Binding-URL.html" 
title="Chapter&#160;8.&#160;Binding URL">Binding URL</a>.
         </p></li></ul></div><p>
     </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 
class="title">Note</h3><p>
         For  <code class="literal">AMQQueue</code> and <code 
class="literal">AMQTopic</code> prefix <code class="literal">BURL:</code> need
         to be specified for <a class="link" 
href="JMS-Client-0-8-Binding-URL.html" title="Chapter&#160;8.&#160;Binding 
URL">Binding URL</a>. Otherwise, client will try
-        to parse content using <a class="ulink" 
href="../../Programming-In-Apache-Qpid/html/" target="_top">Address</a> format.
+        to parse content using <a class="link" 
href="/releases/qpid-0.32/programming/book/" target="_top">Address</a> format.
       </p></div><p>
   </p><p>An example below demonstrates how to create JNDI resources in the 
Tomcat container using Resource declarations in context.xml
     (A Tomcat specific web application configuration file usually added into 
war under /META-INF/context.xml).
-  </p><div class="example"><a id="idm139643147487248"></a><p 
class="title"><strong>Example&#160;E.1.&#160;An example of Tomcat context.xml 
declaring Qpid JNDI resources</strong></p><div class="example-contents"><pre 
class="programlisting">
+  </p><div class="example"><a id="d0e3215"></a><p 
class="title"><strong>Example&#160;E.1.&#160;An example of Tomcat context.xml 
declaring Qpid JNDI resources</strong></p><div class="example-contents"><pre 
class="programlisting">
 &lt;?xml version='1.0' encoding='utf-8'?&gt;
 &lt;!DOCTYPE xml&gt;
 &lt;Context&gt;
@@ -197,7 +197,7 @@ https://github.com/apache/qpid-proton/bl
     20 and 60000 milliseconds accordingly.
   </p><p>
     The client application can find the resources declared in Tomcat 
context.xml using the code below:
-  </p><div class="example"><a id="idm139643146512336"></a><p 
class="title"><strong>Example&#160;E.2.&#160;An example of JNDI lookup for Qpid 
resources registered in Tomcat JNDI</strong></p><div 
class="example-contents"><pre class="programlisting">
+  </p><div class="example"><a id="d0e3239"></a><p 
class="title"><strong>Example&#160;E.2.&#160;An example of JNDI lookup for Qpid 
resources registered in Tomcat JNDI</strong></p><div 
class="example-contents"><pre class="programlisting">
     Context context = new InitialContext();
     Context environmentContext = (Context)context.lookup("java:comp/env");
     ...
@@ -208,14 +208,14 @@ https://github.com/apache/qpid-proton/bl
     Topic topic = (Topic)environmentContext.lookup("jms/topic");
     ...</pre></div></div><br class="example-break" /><div class="note" 
style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
       In order to support backward compatibility <code 
class="literal">AMQConnectionFactory</code> continues to implement
-      <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/spi/ObjectFactory.html";
 target="_top">javax.naming.spi.ObjectFactory</a>
+      <a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/spi/ObjectFactory.html";
 target="_top">javax.naming.spi.ObjectFactory</a>
       and can be used to instantiate JNDI resources from
-      <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Reference.html"; 
target="_top">javax.naming.Reference</a>s.
+      <a class="link" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/Reference.html"; 
target="_top">javax.naming.Reference</a>s.
       However, its method <code class="literal">getObjectInstance</code> is 
marked as <code class="literal">Deprecated</code> and will be
       removed in future version of client. For backward compatibility, Qpid 
JNDI resources can be declared using fully
       qualified class names as addresses. That will became unsupported in 
future version as well.
       An example of Tomcat context.xml with declarations of JNDI resources 
using deprecated factory and addresses is provided below.
-  </p><div class="example"><a id="idm139643146505648"></a><p 
class="title"><strong>Example&#160;E.3.&#160;An example of Tomcat context.xml 
declaring Qpid JNDI resources using deprecated <code 
class="literal">ObjectFactory</code> and deprecated addresses</strong></p><div 
class="example-contents"><pre class="programlisting">
+  </p><div class="example"><a id="d0e3262"></a><p 
class="title"><strong>Example&#160;E.3.&#160;An example of Tomcat context.xml 
declaring Qpid JNDI resources using deprecated <code 
class="literal">ObjectFactory</code> and deprecated addresses</strong></p><div 
class="example-contents"><pre class="programlisting">
 &lt;?xml version='1.0' encoding='utf-8'?&gt;
 &lt;!DOCTYPE xml&gt;
 &lt;Context&gt;
@@ -236,7 +236,7 @@ https://github.com/apache/qpid-proton/bl
             
org.apache.qpid.client.AMQConnectionFactory="amqp://guest:guest@clientid/?brokerlist='localhost:5672'"/&gt;
 
 &lt;/Context&gt;</pre></div></div><p><br class="example-break" />
-    </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-Appendix-PooledConnecytionFactory.html">Prev</a>&#160;</td><td
 align="center" width="20%">&#160;</td><td align="right" 
width="40%">&#160;</td></tr><tr><td align="left" valign="top" 
width="40%">Appendix&#160;D.&#160;PooledConnectionFactory&#160;</td><td 
align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td 
align="right" valign="top" width="40%">&#160;</td></tr></table></div></div>
+    </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-Appendix-PooledConnecytionFactory.html">Prev</a>&#160;</td><td
 align="center" width="20%">&#160;</td><td align="right" 
width="40%">&#160;</td></tr><tr><td align="left" valign="top" 
width="40%">Appendix&#160;D.&#160;PooledConnectionFactory&#160;</td><td 
align="center" width="20%"><a accesskey="h" 
href="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html
URL: 
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html
 Sat Jan  2 23:59:48 2016
@@ -114,10 +114,10 @@ https://github.com/apache/qpid-proton/bl
         <ul id="-path-navigation"><li><a 
href="/index.html">Home</a></li><li><a 
href="/releases/index.html">Releases</a></li><li><a 
href="/releases/qpid-java-trunk/index.html">Qpid Java Trunk</a></li><li><a 
href="/releases/qpid-java-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>Chapter&#160;8.&#160;Binding 
URL</li></ul>
 
         <div id="-middle-content">
-          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">Chapter&#160;8.&#160;Binding URL</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Connection-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-System-Properties.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-Binding-URL"></a>Chapter&#160;8.&#160;Binding 
URL</h1></div></div></div><div class="toc"><p><strong>Table of 
Contents</strong></p><dl class="toc"><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-Examples">8.1. 
Binding URL Examples</a></span></dt><dd><dl><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-JMS-Queues">8.1.1.
 Binding URLs for declar
 ing of JMS Queues</a></span></dt><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-JMS-Topics">8.1.2.
 Binding URLs for declaring of JMS Topics</a></span></dt><dt><span 
class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-Topics-Wildcards">8.1.3.
 Wildcard characters in routing keys for topic 
destinations</a></span></dt><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-Extra-Examples">8.1.4.
 More Examples</a></span></dt></dl></dd></dl></div><p> The <span 
class="emphasis"><em>Binding URL</em></span> syntax for addressing<a 
class="footnote" href="#ftn.idm139643150444640" id="idm139643150444640"><sup 
class="footnote">[4]</sup></a>. It allows the specification of the bindings 
between a queue and an exchange, queue
+          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">Chapter&#160;8.&#160;Binding URL</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Connection-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-Message-Encryption.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-Binding-URL"></a>Chapter&#160;8.&#160;Binding 
URL</h1></div></div></div><div class="toc"><p><strong>Table of 
Contents</strong></p><dl class="toc"><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-Examples">8.1. 
Binding URL Examples</a></span></dt><dd><dl><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-JMS-Queues">8.1.1.
 Binding URLs for declaring
  of JMS Queues</a></span></dt><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-JMS-Topics">8.1.2.
 Binding URLs for declaring of JMS Topics</a></span></dt><dt><span 
class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-Topics-Wildcards">8.1.3.
 Wildcard characters in routing keys for topic 
destinations</a></span></dt><dt><span class="section"><a 
href="JMS-Client-0-8-Binding-URL.html#JMS-Client-0-8-Binding-URL-Extra-Examples">8.1.4.
 More Examples</a></span></dt></dl></dd></dl></div><p> The <span 
class="emphasis"><em>Binding URL</em></span> syntax for addressing<a 
class="footnote" href="#ftn.d0e1546" id="d0e1546"><sup 
class="footnote">[4]</sup></a>. It allows the specification of the bindings 
between a queue and an exchange, queue
     and exchange creation arguments and some ancillary options.</p><p> The 
format for a <span class="emphasis"><em>Binding URL</em></span> is provided 
below </p><pre class="screen">
 &lt;Exchange Class&gt;://&lt;Exchange 
Name&gt;/[&lt;Destination&gt;]/[&lt;Queue&gt;][?&lt;option&gt;='&lt;value&gt;'[&amp;&lt;option&gt;='&lt;value&gt;']]
-    </pre><p> where </p><div class="itemizedlist"><ul class="itemizedlist" 
type="disc"><li class="listitem"><p><span class="emphasis"><em>Exchange 
Class</em></span>, specifies the type of the exchange, for example,
+    </pre><p> where </p><div class="itemizedlist"><ul class="itemizedlist" 
style="list-style-type: disc; "><li class="listitem"><p><span 
class="emphasis"><em>Exchange Class</em></span>, specifies the type of the 
exchange, for example,
             <span class="emphasis"><em>direct</em></span>,<span 
class="emphasis"><em>topic</em></span>,<span 
class="emphasis"><em>fanout</em></span>, etc.
         </p></li><li class="listitem"><p><span class="emphasis"><em>Exchange 
Name</em></span>, specifies the name of the exchange, for example,
             <span class="emphasis"><em>amq.direct</em></span>,<span 
class="emphasis"><em>amq.topic</em></span>, etc. </p></li><li 
class="listitem"><p><span class="emphasis"><em>Destination</em></span>, is an 
optional part of <span class="emphasis"><em>Binding
@@ -129,7 +129,7 @@ https://github.com/apache/qpid-proton/bl
           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="idm139643152477776"></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="d0e1634"></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
@@ -151,8 +151,9 @@ https://github.com/apache/qpid-proton/bl
                 The consumer behaves like a queue browser in this 
case.</p></td></tr><tr><td><a 
id="JMS-Client-0-8-Binding-URL-Options-RejectBehaviour"></a><p>rejectbehaviour</p></td><td><p>string
 </p></td><td><p>Defines the reject behaviour for the re-delivered messages. If 
set to
                 'SERVER' the client delegates the requeue/DLQ decision to the 
server. If this option
                 is not specified, the messages won't be moved to the DLQ (or 
dropped) when delivery
-                count exceeds the maximum. 
</p></td></tr></tbody></table></div></div><p><br class="table-break" />
-  </p><div class="section"><div class="titlepage"><div><div><h2 
class="title"><a id="JMS-Client-0-8-Binding-URL-Examples"></a>8.1.&#160;Binding 
URL Examples</h2></div></div></div><div class="section"><div 
class="titlepage"><div><div><h3 class="title"><a 
id="JMS-Client-0-8-Binding-URL-JMS-Queues"></a>8.1.1.&#160;Binding URLs for 
declaring of JMS Queues</h3></div></div></div><p>The Qpid client Binding URLs 
for JMS queue destinations can be declared using direct
+                count exceeds the maximum. </p></td></tr><tr><td><a 
id="JMS-Client-0-8-Binding-URL-Options-SendEncrypted"></a><p>sendencrypted</p></td><td><p>boolean
 </p></td><td><p>If true then encrypt every message sent to this address. 
</p></td></tr><tr><td><a 
id="JMS-Client-0-8-Binding-URL-Options-EncryptedRecipients"></a><p>encryptedrecipients</p></td><td><p>string
 </p></td><td><p>A semi-colon separated list of the names of the recipients who 
will be able to decrypt the
+                    message. </p></td></tr></tbody></table></div></div><p><br 
class="table-break" />
+  </p><div class="section"><div class="titlepage"><div><div><h2 class="title" 
style="clear: both"><a 
id="JMS-Client-0-8-Binding-URL-Examples"></a>8.1.&#160;Binding URL 
Examples</h2></div></div></div><div class="section"><div 
class="titlepage"><div><div><h3 class="title"><a 
id="JMS-Client-0-8-Binding-URL-JMS-Queues"></a>8.1.1.&#160;Binding URLs for 
declaring of JMS Queues</h3></div></div></div><p>The Qpid client Binding URLs 
for JMS queue destinations can be declared using direct
         exchange (Mostly it is a pre-defined exchange with a name 
"amq.direct". Also, custom direct
         exchanges can be used.): </p><pre class="screen">
 direct://amq.direct//&lt;Queue Name&gt;
@@ -160,7 +161,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="idm139643150250704"></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="d0e1790"></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'
@@ -172,7 +173,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="idm139643150245152"></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="d0e1808"></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
@@ -186,9 +187,9 @@ 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="idm139643146536800"></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="d0e1833"></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 class="footnotes"><br /><hr align="left" width="100" /><div 
class="footnote" id="ftn.idm139643150444640"><p><a class="para" 
href="#idm139643150444640"><sup class="para">[4] </sup></a>The client also 
supports the ADDR format. This is documented in <a class="ulink" 
href="../../Programming-In-Apache-Qpid/html/" target="_top">Programming in 
Apache Qpid</a>.</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-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" widt
 h="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>
+                  "custom.topic" of class "topic" using binding key 
"aq".</p></td></tr></tbody></table></div></div><br class="table-break" 
/></div></div><div class="footnotes"><br /><hr style="width:100; 
text-align:left;margin-left: 0" /><div class="footnote" id="ftn.d0e1546"><p><a 
class="para" href="#d0e1546"><sup class="para">[4] </sup></a>The client also 
supports the ADDR format. This is documented in <a class="link" 
href="/releases/qpid-0.32/programming/book/" target="_top">Programming in 
Apache Qpid</a>.</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-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-Message-Encryption.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="JMS-Client-Book.html">Home</a></td><td 
align="right" valign="top" width="40%">&#160;Chapter&#160;9.&#160;Message 
Encryption</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-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-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html
 Sat Jan  2 23:59:48 2016
@@ -114,12 +114,12 @@ https://github.com/apache/qpid-proton/bl
         <ul id="-path-navigation"><li><a 
href="/index.html">Home</a></li><li><a 
href="/releases/index.html">Releases</a></li><li><a 
href="/releases/qpid-java-trunk/index.html">Qpid Java Trunk</a></li><li><a 
href="/releases/qpid-java-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 id="-middle-content">
-          <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.idm139643147275664" id="idm139643147275664"><sup 
class="footnote">[3]</sup></a>.</p><p>Each connection utilises a single TCP/IP 
connection between the process of the application
+          <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" style="clear: both"><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.d0e384" id="d0e384"><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
-      is closed when the application calls <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html#close()" 
target="_top">Connection#close()</a>, but it
+      is closed when the application calls <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html#close()" 
target="_top">Connection#close()</a>, but it
       can also be closed if the connection is closed from the Broker side (via 
a Management
       operation or broker shutdown or running into conditions which AMQP 
specifications treats as
       errors and mandates closing the connection). The JMS connection will 
also be closed if the
@@ -129,23 +129,23 @@ https://github.com/apache/qpid-proton/bl
         broker list.</p><p>This failover process is done in a manner that is 
mostly transparent to the application.
         After a successful failover, any existing Connection, Session, 
MessageConsumer and
         MessageProducer objects held by the application remain valid.</p><p>If 
a failover occurs during the scope of a JMS Transaction, any work performed by 
that
-        transaction is lost. The application is made aware of this loss by way 
of the <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/TransactionRolledBackException.html";
 target="_top">TransactionRolledBackException</a> from the <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Session.html#commit"; 
target="_top">Session#commit()</a> call.
+        transaction is lost. The application is made aware of this loss by way 
of the <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/TransactionRolledBackException.html";
 target="_top">TransactionRolledBackException</a> from the <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Session.html#commit"; 
target="_top">Session#commit()</a> call.
         Applications utilising failover must be prepared to catch this 
exception and respond by
         either repeating the work of the transaction, or by propagating a 
rollback to the
         originating system.</p><p>If, after all retries are exhausted, 
failover has failed to reconnect the application,
-        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 <a class="ulink" 
href="JMS-Client-0-8-Appendix-Exceptions-AMQDisconnectedException" 
target="_top">AMQDisconnectedException</a>. 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>Configure failover using the 
Connection URL. Here's an example Connection URL utilising
+        the Connection's <a class="link" 
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 <a class="link" 
href="JMS-Client-0-8-Appendix-Exceptions-AMQDisconnectedException" 
target="_top">AMQDisconnectedException</a>. Any further use of the JMS objects 
(Connection, Session
+        etc), will results in a <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/IllegalStateException.html"; 
target="_top">IllegalStateException</a>.</p><p>Configure failover using the 
Connection URL. Here's an example Connection URL utilising
         failover between two brokers. Note the use of the broker options <a 
class="link" 
href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-Retries"><code
 class="literal">retries</code></a> and <a class="link" 
href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-ConnectDelay"><code
 class="literal">connectdelay</code></a> to control the number of connection 
attempts to
         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="idm139643150896736"></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="d0e439"></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
-            <code class="literal">nofailover</code> as in the example below 
</p><div class="example"><a id="idm139643150892544"></a><p 
class="title"><strong>Example&#160;5.2.&#160;Connection URL configured with 
nofailover</strong></p><div class="example-contents"><pre class="screen">
+            <code class="literal">nofailover</code> as in the example below 
</p><div class="example"><a id="d0e453"></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" />
@@ -157,25 +157,25 @@ amqp://username:password@clientid/test
           <span class="emphasis"><em>minimally</em></span> responsive. (It 
does nothing however to determine the
         health of the higher level tiers of application, for this reason, 
applications may implement
         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
+        automatically closed and the Connection's <a class="link" 
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="idm139643151058032"></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="link" 
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="d0e489"></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="idm139643151053152"></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">
+        be configured on the Broker.</p><p>Some example Connection URLs using 
SSL follow:</p><div class="itemizedlist"><ul class="itemizedlist" 
style="list-style-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="d0e505"></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="idm139643151048112"></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="d0e521"></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="idm139643150880128"></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="d0e537"></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?key_store='/path/to/app1_client_cert.ks'&amp;key_store_password='secret''&amp;ssl='true'
             </pre></div></div><br class="example-break" /><p>Alternatively we 
can use <a class="link" 
href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-ClientCertPath"><code
 class="literal">client_cert_path</code></a> and <a class="link" 
href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-BrokerOptions-ClientCertPrivKeyPath"><code
 class="literal">client_cert_priv_key_ath</code></a> to specify a path to a 
certificate file (in PEM or DER format)
-            and the private key information (again in either PEM or DER 
format) respectively.</p><div class="example"><a id="idm139643150875456"></a><p 
class="title"><strong>Example&#160;5.7.&#160;Connection URL configured for SSL 
- SSL client-auth (2)</strong></p><div class="example-contents"><pre 
class="screen">
+            and the private key information (again in either PEM or DER 
format) respectively.</p><div class="example"><a id="d0e552"></a><p 
class="title"><strong>Example&#160;5.7.&#160;Connection URL configured for SSL 
- SSL client-auth (2)</strong></p><div class="example-contents"><pre 
class="screen">
 
amqp://guest:guest@clientid/?brokerlist='localhost:5671?client_cert_path='/path/to/app1_client.crt'&amp;client_cert_priv_key_path='/path/to/app1_client.key''&amp;ssl='true'
             </pre></div></div><br class="example-break" 
/></li></ul></div></div><div class="section"><div 
class="titlepage"><div><div><h3 class="title"><a 
id="JMS-Client-0-8-Client-Understanding-Connection-MessageCompression"></a>5.3.4.&#160;Message
 Compression</h3></div></div></div><p>The client has the ability to 
transparently compress message payloads on outgoing
         messages and decompress them on incoming messages. In some 
environments and with some
@@ -185,7 +185,7 @@ amqp://guest:guest@clientid/?brokerlist=
         message payloads. See connection url property <a class="link" 
href="JMS-Client-0-8-Connection-URL.html#JMS-Client-0-8-Connection-URL-ConnectionOptions-MessageCompressionThresholdSize"><code
 class="literal">messageCompressionThresholdSize</code></a> (or JVM wide using 
the system
         property <a class="link" 
href="JMS-Client-0-8-System-Properties.html#JMS-Client-0-8-System-Properties-MessageCompressionThresholdSize"><code
 class="literal">qpid.message_compression_threshold_size</code></a>)</p><div 
class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 
class="title">Note</h3><p>The Broker, where necessary, takes care of 
compressing/decompressing messages of the
           fly so that clients using message compression can exchange messages 
with clients not
-          supporting message compression transparently, without application 
intervention.</p></div></div><div class="footnotes"><br /><hr align="left" 
width="100" /><div class="footnote" id="ftn.idm139643147275664"><p><a 
class="para" href="#idm139643147275664"><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>
+          supporting message compression transparently, without application 
intervention.</p></div></div><div class="footnotes"><br /><hr style="width:100; 
text-align:left;margin-left: 0" /><div class="footnote" id="ftn.d0e384"><p><a 
class="para" href="#d0e384"><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="JMS-Client-Book.html">Home</a></td><td a
 lign="right" valign="top" 
width="40%">&#160;5.4.&#160;Session</td></tr></table></div></div>
 
           <hr/>
 

Modified: 
qpid/site/docs/releases/qpid-java-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-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html?rev=1722689&r1=1722688&r2=1722689&view=diff
==============================================================================
--- 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html
 (original)
+++ 
qpid/site/docs/releases/qpid-java-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html
 Sat Jan  2 23:59:48 2016
@@ -114,14 +114,14 @@ https://github.com/apache/qpid-proton/bl
         <ul id="-path-navigation"><li><a 
href="/index.html">Home</a></li><li><a 
href="/releases/index.html">Releases</a></li><li><a 
href="/releases/qpid-java-trunk/index.html">Qpid Java Trunk</a></li><li><a 
href="/releases/qpid-java-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.2.&#160;ConnectionFactory</li></ul>
 
         <div id="-middle-content">
-          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">5.2.&#160;ConnectionFactory</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Client-Understanding.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-Connection.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-ConnectionFactory"></a>5.2.&#160;ConnectionFactory</h2></div></div></div><p>A
 <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/ConnectionFactory.html"; 
target="_top">ConnectionFactory</a>
-      allows an application to create a <a class="ulink" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html"; 
target="_top">Connection</a>.</p><p>The application obtains the 
ConnectionFactory from an <a class="ulink" 
href="http://docs.oracle.com/javase/7/docs/api/javax/naming/InitialContext.html";
 target="_top">InitialContext</a>. The
+          <div class="docbook"><div class="navheader"><table 
summary="Navigation header" width="100%"><tr><th align="center" 
colspan="3">5.2.&#160;ConnectionFactory</th></tr><tr><td align="left" 
width="20%"><a accesskey="p" 
href="JMS-Client-0-8-Client-Understanding.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-Connection.html">Next</a></td></tr></table><hr
 /></div><div class="section"><div class="titlepage"><div><div><h2 
class="title" style="clear: both"><a 
id="JMS-Client-0-8-Client-Understanding-ConnectionFactory"></a>5.2.&#160;ConnectionFactory</h2></div></div></div><p>A
 <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/ConnectionFactory.html"; 
target="_top">ConnectionFactory</a>
+      allows an application to create a <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html"; 
target="_top">Connection</a>.</p><p>The application obtains the 
ConnectionFactory from an <a class="link" 
href="http://docs.oracle.com/javaee/6/api/javax/naming/InitialContext.html"; 
target="_top">InitialContext</a>. The
       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/7/docs/api/java/util/Properties.html"; 
target="_top">Properties</a> object which can of course be loaded from an 
external properties file,
+      implementation is backed by a <a class="link" 
href="http://docs.oracle.com/javaee/6/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>The Qpid JMS client also 
provides an alternate connection factory implementation providing a
-      connection pool. This can be useful when utilsing frameworks such as 
Spring. 
-      <a class="xref" 
href="JMS-Client-0-8-Appendix-PooledConnecytionFactory.html" 
title="Appendix&#160;D.&#160;PooledConnectionFactory">Appendix&#160;D, 
<em>PooledConnectionFactory</em></a>.</p><div class="figure"><a 
id="idm139643147666656"></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" /><p>Note that the Qpid Broker does not present a JNDI 
interface to the application.</p></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>
+      connection pool. This can be useful when utilsing frameworks such as 
Spring.
+      <a class="xref" 
href="JMS-Client-0-8-Appendix-PooledConnecytionFactory.html" 
title="Appendix&#160;D.&#160;PooledConnectionFactory">Appendix&#160;D, 
<em>PooledConnectionFactory</em></a>.</p><div class="figure"><a 
id="d0e369"></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" /><p>Note that the Qpid Broker does not present a JNDI 
interface to the application.</p></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
 ali
 gn="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="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" 
width="40%">&#160;5.3.&#160;Connection</td></tr></table></div></div>
 
           <hr/>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to