You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ro...@apache.org on 2012/02/19 23:51:48 UTC

svn commit: r1291086 - /qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml

Author: robbie
Date: Sun Feb 19 22:51:48 2012
New Revision: 1291086

URL: http://svn.apache.org/viewvc?rev=1291086&view=rev
Log:
NO-JIRA: improve cross referencing of config options

Modified:
    qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml

Modified: qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml
URL: http://svn.apache.org/viewvc/qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml?rev=1291086&r1=1291085&r2=1291086&view=diff
==============================================================================
--- qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml (original)
+++ qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml Sun Feb 19 22:51:48 2012
@@ -3580,7 +3580,7 @@ log4j.appender.console.layout.Conversion
 	              <entry>qpid.heartbeat</entry>
 	              <entry>int</entry>
 	              <entry>120 (secs)</entry>
-                  <entry>The heartbeat interval in seconds. Two consective misssed heartbeats will result in the connection timing out.<para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry>The heartbeat interval in seconds. Two consective misssed heartbeats will result in the connection timing out.<para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
 	            <row>
@@ -3624,7 +3624,7 @@ log4j.appender.console.layout.Conversion
 	              <entry>qpid.use_legacy_map_message</entry>
 	              <entry>boolean</entry>
 	              <entry>false</entry>
-                  <entry><para>If set will use the old map message encoding. By default the Map messages are encoded using the 0-10 map encoding.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>If set will use the old map message encoding. By default the Map messages are encoded using the 0-10 map encoding.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
                 <row>
@@ -3674,7 +3674,7 @@ log4j.appender.console.layout.Conversion
 	              <entry>sync_ack</entry>
 	              <entry>boolean</entry>
 	              <entry>false</entry>
-                  <entry><para>If set, each message will be acknowledged synchronously. When using AUTO_ACK mode, you need to set this to "true", in order to get the correct behaviour as described by the JMS spec.</para><para>This is set to false by default for performance reasons, therefore by default AUTO_ACK behaves similar to DUPS_OK.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>If set, each message will be acknowledged synchronously. When using AUTO_ACK mode, you need to set this to "true", in order to get the correct behaviour as described by the JMS spec.</para><para>This is set to false by default for performance reasons, therefore by default AUTO_ACK behaves similar to DUPS_OK.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
               </tbody>
             </tgroup>
@@ -3696,7 +3696,7 @@ log4j.appender.console.layout.Conversion
 	              <entry>sync_publish</entry>
 	              <entry>string</entry>
 	              <entry>"" (disabled)</entry>
-                  <entry><para>If one of {persistent|all} is set then persistent messages or all messages will be sent synchronously.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>If one of {persistent|all} is set then persistent messages or all messages will be sent synchronously.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
               </tbody>
             </tgroup>
@@ -3781,21 +3781,21 @@ log4j.appender.console.layout.Conversion
 	              <entry>qpid.sasl_mechs</entry>
 	              <entry>string</entry>
 	              <entry>PLAIN</entry>
-                  <entry><para>The SASL mechanism to be used. More than one could be specified as a comma separated list.</para><para>We currently support the following mechanisms {PLAIN | GSSAPI | EXTERNAL}.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>The SASL mechanism to be used. More than one could be specified as a comma separated list.</para><para>We currently support the following mechanisms {PLAIN | GSSAPI | EXTERNAL}.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
 	            <row>
 	              <entry>qpid.sasl_protocol</entry>
 	              <entry>string</entry>
 	              <entry>AMQP</entry>
-                  <entry><para>When using GSSAPI as the SASL mechanism, <varname>sasl_protocol</varname> must be set to the principal for the qpidd broker, e.g. <varname>qpidd</varname>.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>When using GSSAPI as the SASL mechanism, <varname>sasl_protocol</varname> must be set to the principal for the qpidd broker, e.g. <varname>qpidd</varname>.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
 	            <row>
 	              <entry>qpid.sasl_server_name</entry>
 	              <entry>string</entry>
 	              <entry>localhost</entry>
-                  <entry><para>When using GSSAPI as the SASL mechanism, <varname>sasl_server</varname> must be set to the host for the SASL server, e.g. <varname>example.com</varname>.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>When using GSSAPI as the SASL mechanism, <varname>sasl_server</varname> must be set to the host for the SASL server, e.g. <varname>example.com</varname>.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
               </tbody>
             </tgroup>
@@ -3895,28 +3895,28 @@ log4j.appender.console.layout.Conversion
 	              <entry>javax.net.ssl.keyStore</entry>
 	              <entry>string</entry>
 	              <entry>jvm default</entry>
-                  <entry><para>Specifies the key store path.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>Specifies the key store path.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
                 <row>
 	              <entry>javax.net.ssl.keyStorePassword</entry>
 	              <entry>string</entry>
 	              <entry>jvm default</entry>
-                  <entry><para>Specifies the key store password.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>Specifies the key store password.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
 	            <row>
 	              <entry>javax.net.ssl.trustStore</entry>
 	              <entry>string</entry>
 	              <entry>jvm default</entry>
-                  <entry><para>Specifies the trust store path.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>Specifies the trust store path.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
 
                 <row>
 	              <entry>javax.net.ssl.trustStorePassword</entry>
 	              <entry>string</entry>
 	              <entry>jvm default</entry>
-                  <entry><para>Specifies the trust store password.</para><para>This could also be set per connection as well (see connection paramters).</para></entry>
+                  <entry><para>Specifies the trust store password.</para><para>This can also be set per connection using the <link linkend="section-jms-connection-url">Connection URL</link> options.</para></entry>
                 </row>
               </tbody>
             </tgroup>



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