Author: robbie
Date: Mon Jun 15 16:04:54 2015
New Revision: 1685611
URL: http://svn.apache.org/r1685611
Log:
NO-JIRA: update website for Qpid JMS client 0.3.0 release
Added:
qpid/site/docs/releases/qpid-jms-0.3.0/
qpid/site/docs/releases/qpid-jms-0.3.0/building.html
- copied, changed from r1683498, qpid/site/docs/maven.html
qpid/site/docs/releases/qpid-jms-0.3.0/docs/
qpid/site/docs/releases/qpid-jms-0.3.0/docs/index.html
qpid/site/docs/releases/qpid-jms-0.3.0/index.html
- copied, changed from r1683498,
qpid/site/docs/releases/qpid-jms-0.2.0/index.html
qpid/site/docs/releases/qpid-jms-0.3.0/release-notes.html
- copied, changed from r1683498,
qpid/site/docs/releases/qpid-jms-0.2.0/index.html
qpid/site/input/releases/qpid-jms-0.3.0/
qpid/site/input/releases/qpid-jms-0.3.0/building.md
qpid/site/input/releases/qpid-jms-0.3.0/docs/
qpid/site/input/releases/qpid-jms-0.3.0/docs/index.md
qpid/site/input/releases/qpid-jms-0.3.0/index.md
qpid/site/input/releases/qpid-jms-0.3.0/release-notes.md
Modified:
qpid/site/docs/components/jms/index.html
qpid/site/docs/documentation.html
qpid/site/docs/download.html
qpid/site/docs/maven.html
qpid/site/docs/releases/index.html
qpid/site/docs/releases/qpid-jms-0.1.0/index.html
qpid/site/docs/releases/qpid-jms-0.2.0/index.html
qpid/site/input/_config.ini
qpid/site/input/releases/index.md
Modified: qpid/site/docs/components/jms/index.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/components/jms/index.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/components/jms/index.html (original)
+++ qpid/site/docs/components/jms/index.html Mon Jun 15 16:04:54 2015
@@ -136,9 +136,9 @@ API compatible</li>
<ul>
<li><a
href="http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html";>API
reference</a></li>
-<li><a
href="https://github.com/apache/qpid-jms/tree/0.2.0/qpid-jms-examples";>Examples</a></li>
-<li><a href="/releases/qpid-jms-0.2.0/docs/index.html">Configuration</a></li>
-<li><a href="/releases/qpid-jms-0.2.0/building.html">Building Qpid JMS</a></li>
+<li><a
href="https://github.com/apache/qpid-jms/tree/0.3.0/qpid-jms-examples";>Examples</a></li>
+<li><a href="/releases/qpid-jms-0.3.0/docs/index.html">Configuration</a></li>
+<li><a href="/releases/qpid-jms-0.3.0/building.html">Building Qpid JMS</a></li>
</ul>
</div>
@@ -152,7 +152,7 @@ API compatible</li>
<h2 id="releases">Releases</h2>
<ul>
-<li><a href="/releases/qpid-jms-0.2.0/index.html">Qpid JMS 0.2.0</a></li>
+<li><a href="/releases/qpid-jms-0.3.0/index.html">Qpid JMS 0.3.0</a></li>
<li><a href="/releases/index.html#past-releases">Past releases</a></li>
</ul>
Modified: qpid/site/docs/documentation.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/documentation.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/documentation.html (original)
+++ qpid/site/docs/documentation.html Mon Jun 15 16:04:54 2015
@@ -107,7 +107,7 @@
<p>The documentation on this page is for our current releases,
<a href="/releases/qpid-0.32/index.html">Qpid 0.32</a>, <a
href="/releases/qpid-proton-0.9.1/index.html">Qpid Proton 0.9.1</a>,
-<a href="/releases/qpid-dispatch-0.4/index.html">Qpid Dispatch 0.4</a>, and <a
href="/releases/qpid-jms-0.2.0/index.html">Qpid JMS 0.2.0</a>. You can find
older versions with our
+<a href="/releases/qpid-dispatch-0.4/index.html">Qpid Dispatch 0.4</a>, and <a
href="/releases/qpid-jms-0.3.0/index.html">Qpid JMS 0.3.0</a>. You can find
older versions with our
<a href="/releases/index.html#past-releases">past releases</a>.</p>
<hr />
Modified: qpid/site/docs/download.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/download.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/download.html (original)
+++ qpid/site/docs/download.html Mon Jun 15 16:04:54 2015
@@ -111,7 +111,7 @@
<p>Qpid's source artefacts are produced as part of our community release
process. The downloads on this page are from our current releases,
<a href="/releases/qpid-0.32/index.html">Qpid 0.32</a>, <a
href="/releases/qpid-proton-0.9.1/index.html">Qpid Proton 0.9.1</a>,
-<a href="/releases/qpid-dispatch-0.4/index.html">Qpid Dispatch 0.4</a>, and <a
href="/releases/qpid-jms-0.2.0/index.html">Qpid JMS 0.2.0</a>. You can also see
our
+<a href="/releases/qpid-dispatch-0.4/index.html">Qpid Dispatch 0.4</a>, and <a
href="/releases/qpid-jms-0.3.0/index.html">Qpid JMS 0.3.0</a>. You can also see
our
<a href="/releases/index.html#past-releases">past releases</a>.</p>
<p>It's important to <a href="#verify-what-you-download">verify the
integrity</a> of the files you download.</p>
@@ -122,7 +122,7 @@ process. The downloads on this page are
<tbody>
<tr><td><em>Content</em></td><td><em>Download</em></td><td><em>Verify</em></td></tr>
<tr><td><a href="/proton/index.html">Qpid Proton</a></td><td><a
href="http://www.apache.org/dyn/closer.cgi/qpid/proton/0.9.1/qpid-proton-0.9.1.tar.gz";>qpid-proton-0.9.1.tar.gz</a></td><td><a
href="http://www.apache.org/dist/qpid/proton/0.9.1/qpid-proton-0.9.1.tar.gz.asc";>ASC</a>,
<a
href="http://www.apache.org/dist/qpid/proton/0.9.1/qpid-proton-0.9.1.tar.gz.md5";>MD5</a>,
<a
href="http://www.apache.org/dist/qpid/proton/0.9.1/qpid-proton-0.9.1.tar.gz.sha";>SHA</a></td></tr>
-<tr><td><a href="/components/jms/index.html">Qpid JMS</a> (AMQP
1.0)</td><td><a
href="http://www.apache.org/dyn/closer.cgi/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz";>apache-qpid-jms-0.2.0-bin.tar.gz</a>*^</td><td><a
href="http://www.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.asc";>ASC</a>,
<a
href="http://www.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.md5";>MD5</a>,
<a
href="http://www.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.sha1";>SHA1</a></td></tr>
+<tr><td><a href="/components/jms/index.html">Qpid JMS</a> (AMQP
1.0)</td><td><a
href="http://www.apache.org/dyn/closer.cgi/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz";>apache-qpid-jms-0.3.0-bin.tar.gz</a>*^</td><td><a
href="http://www.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.asc";>ASC</a>,
<a
href="http://www.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.md5";>MD5</a>,
<a
href="http://www.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.sha1";>SHA1</a></td></tr>
<tr><td><a href="/components/jms/amqp-0-x.html">Qpid AMQP 0-x JMS
Client</a></td><td><a
href="http://www.apache.org/dyn/closer.cgi/qpid/0.32/binaries/qpid-client-0.32-bin.tar.gz";>qpid-client-0.32-bin.tar.gz</a>*</td><td><a
href="http://www.apache.org/dist/qpid/0.32/binaries/qpid-client-0.32-bin.tar.gz.asc";>ASC</a>,
<a
href="http://www.apache.org/dist/qpid/0.32/binaries/qpid-client-0.32-bin.tar.gz.md5";>MD5</a>,
<a
href="http://www.apache.org/dist/qpid/0.32/binaries/qpid-client-0.32-bin.tar.gz.sha1";>SHA1</a></td></tr>
<tr><td><a href="/components/messaging-api/index.html">Qpid Messaging API</a>
(C++, bindings)</td><td><a
href="http://www.apache.org/dyn/closer.cgi/qpid/0.32/qpid-cpp-0.32.tar.gz";>qpid-cpp-0.32.tar.gz</a></td><td><a
href="http://www.apache.org/dist/qpid/0.32/qpid-cpp-0.32.tar.gz.asc";>ASC</a>,
<a
href="http://www.apache.org/dist/qpid/0.32/qpid-cpp-0.32.tar.gz.md5";>MD5</a>,
<a
href="http://www.apache.org/dist/qpid/0.32/qpid-cpp-0.32.tar.gz.sha1";>SHA1</a></td></tr>
<tr><td><a href="/components/messaging-api/index.html">Qpid Messaging API</a>
(Python)</td><td><a
href="http://www.apache.org/dyn/closer.cgi/qpid/0.32/qpid-python-0.32.tar.gz";>qpid-python-0.32.tar.gz</a></td><td><a
href="http://www.apache.org/dist/qpid/0.32/qpid-python-0.32.tar.gz.asc";>ASC</a>,
<a
href="http://www.apache.org/dist/qpid/0.32/qpid-python-0.32.tar.gz.md5";>MD5</a>,
<a
href="http://www.apache.org/dist/qpid/0.32/qpid-python-0.32.tar.gz.sha1";>SHA1</a></td></tr>
@@ -145,10 +145,10 @@ process. The downloads on this page are
<p>*These Java artefacts are released as compiled bytecode. We also
offer the source as part of our
-<a
href="http://www.apache.org/dyn/closer.cgi/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz";>Qpid
JMS source release</a>
-[<a
href="http://www.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.asc";>ASC</a>,
-<a
href="http://www.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.md5";>MD5</a>,
-<a
href="http://www.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.sha1";>SHA1</a>]
+<a
href="http://www.apache.org/dyn/closer.cgi/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz";>Qpid
JMS source release</a>
+[<a
href="http://www.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.asc";>ASC</a>,
+<a
href="http://www.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.md5";>MD5</a>,
+<a
href="http://www.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.sha1";>SHA1</a>]
and
<a
href="http://www.apache.org/dyn/closer.cgi/qpid/0.32/qpid-java-0.32.tar.gz";>Qpid
Java source release</a>
[<a
href="http://www.apache.org/dist/qpid/0.32/qpid-java-0.32.tar.gz.asc";>ASC</a>,
Modified: qpid/site/docs/maven.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/maven.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/maven.html (original)
+++ qpid/site/docs/maven.html Mon Jun 15 16:04:54 2015
@@ -114,7 +114,7 @@ following dependencies can be added to t
<span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.qpid<span
class="nt"></groupId></span>
<span class="nt"><artifactId></span>qpid-jms-client<span
class="nt"></artifactId></span>
- <span class="nt"><version></span>0.2.0<span
class="nt"></version></span>
+ <span class="nt"><version></span>0.3.0<span
class="nt"></version></span>
<span class="nt"></dependency></span>
</pre></div>
Modified: qpid/site/docs/releases/index.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/index.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/releases/index.html (original)
+++ qpid/site/docs/releases/index.html Mon Jun 15 16:04:54 2015
@@ -114,7 +114,7 @@ and the
<h2 id="current-releases">Current releases</h2>
<ul>
-<li><a href="qpid-jms-0.2.0/index.html">Qpid JMS 0.2.0</a>, May 2015</li>
+<li><a href="qpid-jms-0.3.0/index.html">Qpid JMS 0.3.0</a>, June 2015</li>
<li><a href="qpid-0.32/index.html">Qpid 0.32</a>, March 2015</li>
<li><a href="qpid-dispatch-0.4/index.html">Qpid Dispatch 0.4</a>, April
2015</li>
<li><a href="qpid-proton-0.9.1/index.html">Qpid Proton 0.9.1</a>, May 2015</li>
@@ -123,6 +123,7 @@ and the
<h2 id="past-releases">Past releases</h2>
<ul>
+<li><a href="qpid-jms-0.2.0/index.html">Qpid JMS 0.2.0</a>, May 2015</li>
<li><a href="qpid-jms-0.1.0/index.html">Qpid JMS 0.1.0</a>, March 2015</li>
<li><a href="qpid-proton-0.9/index.html">Qpid Proton 0.9</a>, March 2015</li>
<li><a href="qpid-dispatch-0.3/index.html">Qpid Dispatch 0.3</a>, January
2015</li>
Modified: qpid/site/docs/releases/qpid-jms-0.1.0/index.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-jms-0.1.0/index.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-jms-0.1.0/index.html (original)
+++ qpid/site/docs/releases/qpid-jms-0.1.0/index.html Mon Jun 15 16:04:54 2015
@@ -105,7 +105,7 @@
<ul id="-path-navigation"><li><a
href="/index.html">Home</a></li><li><a
href="/releases/index.html">Releases</a></li><li>Qpid JMS 0.1.0</li></ul>
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.1.0" === "0.2.0") {
+ if ("0.1.0" === "0.3.0") {
_modifyCurrentReleaseLinks();
}
});
Modified: qpid/site/docs/releases/qpid-jms-0.2.0/index.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-jms-0.2.0/index.html?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-jms-0.2.0/index.html (original)
+++ qpid/site/docs/releases/qpid-jms-0.2.0/index.html Mon Jun 15 16:04:54 2015
@@ -105,7 +105,7 @@
<ul id="-path-navigation"><li><a
href="/index.html">Home</a></li><li><a
href="/releases/index.html">Releases</a></li><li>Qpid JMS 0.2.0</li></ul>
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.2.0" === "0.2.0") {
+ if ("0.2.0" === "0.3.0") {
_modifyCurrentReleaseLinks();
}
});
Copied: qpid/site/docs/releases/qpid-jms-0.3.0/building.html (from r1683498,
qpid/site/docs/maven.html)
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-jms-0.3.0/building.html?p2=qpid/site/docs/releases/qpid-jms-0.3.0/building.html&p1=qpid/site/docs/maven.html&r1=1683498&r2=1685611&rev=1685611&view=diff
==============================================================================
--- qpid/site/docs/maven.html (original)
+++ qpid/site/docs/releases/qpid-jms-0.3.0/building.html Mon Jun 15 16:04:54
2015
@@ -21,7 +21,7 @@
-->
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Qpid via Maven - Apache Qpid™</title>
+ <title>QpidJMS - Apache Qpid™</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
@@ -102,45 +102,55 @@
</div>
<div id="-middle" class="panel">
- <ul id="-path-navigation"><li><a
href="/index.html">Home</a></li><li>Qpid via Maven</li></ul>
- <h1 id="qpid-via-maven">Qpid via Maven</h1>
+ <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-jms-0.3.0/index.html">Qpid JMS
0.3.0</a></li><li>QpidJMS</li></ul>
+ <h1 id="qpidjms">QpidJMS</h1>
-<p>The Qpid JMS clients are available via the <a
href="http://search.maven.org/";>Maven central repository</a>. The
-following dependencies can be added to the POM for your Maven build to utilise
the clients.</p>
+<p>The QpidJMS project provides a JMS based client that uses the AMQP v1.0
protocol.</p>
-<h2 id="qpid-jms-amqp-10">Qpid JMS (AMQP 1.0)</h2>
+<p>Below are some quick pointers you might find useful.</p>
-<div class="highlight"><pre>
-<span class="nt"><dependency></span>
- <span class="nt"><groupId></span>org.apache.qpid<span
class="nt"></groupId></span>
- <span class="nt"><artifactId></span>qpid-jms-client<span
class="nt"></artifactId></span>
- <span class="nt"><version></span>0.2.0<span
class="nt"></version></span>
-<span class="nt"></dependency></span>
-</pre></div>
-
-<p>If you are looking for the older AMQP 1.0 JMS client, see <a
href="/components/jms/amqp-1.0-prototype.html">here</a>.</p>
-
-<h2 id="qpid-amqp-0-x-jms-client">Qpid AMQP 0-x JMS Client</h2>
-
-<div class="highlight"><pre>
-<span class="nt"><dependency></span>
- <span class="nt"><groupId></span>org.apache.qpid<span
class="nt"></groupId></span>
- <span class="nt"><artifactId></span>qpid-client<span
class="nt"></artifactId></span>
- <span class="nt"><version></span>0.32<span
class="nt"></version></span>
-<span class="nt"></dependency></span>
-<span class="nt"><dependency></span>
- <span class="nt"><groupId></span>org.apache.geronimo.specs<span
class="nt"></groupId></span>
- <span class="nt"><artifactId></span>geronimo-jms_1.1_spec<span
class="nt"></artifactId></span>
- <span class="nt"><version></span>1.0<span
class="nt"></version></span>
-<span class="nt"></dependency></span>
-</pre></div>
-
-<h2 id="more-information">More information</h2>
-
-<ul>
-<li><a
href="https://repository.apache.org/content/repositories/snapshots/";>Snapshot
repository</a></li>
-<li><a href="http://maven.apache.org/";>Maven project</a></li>
-</ul>
+<h2 id="building-the-code">Building the code</h2>
+
+<p>The project requires Maven 3. Some example commands follow.</p>
+
+<p>Clean previous builds output and install all modules to local repository
without
+running the tests:</p>
+
+<pre><code>mvn clean install -DskipTests
+</code></pre>
+
+<p>Install all modules to the local repository after running all the tests:</p>
+
+<pre><code>mvn clean install
+</code></pre>
+
+<p>Perform a subset tests on the packaged release artifacts without
+installing:</p>
+
+<pre><code>mvn clean verify -Dtest=TestNamePattern*
+</code></pre>
+
+<p>Execute the tests and produce code coverage report:</p>
+
+<pre><code>mvn clean test jacoco:report
+</code></pre>
+
+<h2 id="examples">Examples</h2>
+
+<p>First build and install all the modules as detailed above (if running
against
+a source checkout/release, rather than against released binaries) and then
+consult the README in the qpid-jms-examples module itself.</p>
+
+<h2 id="documentation">Documentation</h2>
+
+<p>There is some basic documentation in the qpid-jms-docs module.</p>
+
+<h2 id="distribution-assemblies">Distribution assemblies</h2>
+
+<p>After building the modules, src and binary distribution assemblies can be
found at:</p>
+
+<pre><code>apache-qpid-jms/target
+</code></pre>
<hr/>
Added: qpid/site/docs/releases/qpid-jms-0.3.0/docs/index.html
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-jms-0.3.0/docs/index.html?rev=1685611&view=auto
==============================================================================
--- qpid/site/docs/releases/qpid-jms-0.3.0/docs/index.html (added)
+++ qpid/site/docs/releases/qpid-jms-0.3.0/docs/index.html Mon Jun 15 16:04:54
2015
@@ -0,0 +1,376 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
+ <head>
+ <title>Client configuration - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
+ <link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
+ <link rel="stylesheet" href="/deferred.css" type="text/css" defer="defer"/>
+ <script type="text/javascript">var _deferredFunctions = [];</script>
+ <script type="text/javascript" src="/deferred.js" defer="defer"></script>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="/ie.css" type="text/css"/>
+ <script type="text/javascript" src="/html5shiv.js"></script>
+ <![endif]-->
+
+ </head>
+ <body>
+ <div id="-content">
+ <div id="-top" class="panel">
+ <a id="-menu-link"><img width="16" height="16"
src="data:image/png;base64," alt="Menu"/></a>
+
+ <a id="-search-link"><img width="22" height="16"
src="data:image/png;base64," alt="Search"/></a>
+
+ <ul id="-global-navigation">
+ <li><a id="-logotype" href="/index.html">Apache
Qpid<sup>™</sup></a></li>
+ <li><a href="/download.html">Download</a></li>
+ <li><a href="/documentation.html">Documentation</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/discussion.html">Discussion</a></li>
+ </ul>
+ </div>
+
+ <div id="-menu" class="panel" style="display: none;">
+ <section>
+ <h3>Project</h3>
+
+ <ul>
+ <li><a href="/overview.html">Overview</a></li>
+ <li><a href="/components/index.html">Components</a></li>
+ <li><a href="/releases/index.html">Releases</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Messaging APIs</h3>
+
+ <ul>
+ <li><a href="/proton/index.html">Qpid Proton</a></li>
+ <li><a href="/components/jms/index.html">Qpid JMS</a></li>
+ <li><a href="/components/messaging-api/index.html">Qpid Messaging
API</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Servers and tools</h3>
+
+ <ul>
+ <li><a href="/components/java-broker/index.html">Java
broker</a></li>
+ <li><a href="/components/cpp-broker/index.html">C++ broker</a></li>
+ <li><a href="/components/dispatch-router/index.html">Dispatch
router</a></li>
+ </ul>
+ </section>
+
+ <section>
+ <h3>Resources</h3>
+
+ <ul>
+ <li><a href="/dashboard.html">Dashboard</a></li>
+ <li><a
href="https://cwiki.apache.org/confluence/display/qpid/Index";>Wiki</a></li>
+ <li><a href="/resources.html">More resources</a></li>
+ </ul>
+ </section>
+ </div>
+
+ <div id="-search" class="panel" style="display: none;">
+ <form action="http://www.google.com/search"; method="get">
+ <input type="hidden" name="sitesearch" value="qpid.apache.org"/>
+ <input type="text" name="q" maxlength="255" autofocus="autofocus"
tabindex="1"/>
+ <button type="submit">Search</button>
+ <p><a href="/search.html">More ways to search</a></p>
+ </form>
+ </div>
+
+ <div id="-middle" class="panel">
+ <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-jms-0.3.0/index.html">Qpid JMS 0.3.0</a></li><li>Client
configuration</li></ul>
+ <h1 id="client-configuration">Client configuration</h1>
+
+<p>This file details various configuration options for the client, such as how
to configure and create a JNDI InitialContext, the syntax for its related
configuration, and various URI options that can be set when defining a
ConnectionFactory.</p>
+
+<h2 id="configuring-a-jndi-initialcontext">Configuring a JNDI
InitialContext</h2>
+
+<p>Applications use a JNDI InitialContext, itself obtained from an
InitialContextFactory, to look up JMS objects such as ConnectionFactory. The
Qpid JMS client provides an implementation of the InitialContextFactory in
class <em>org.apache.qpid.jms.jndi.JmsInitialContextFactory</em>. This may be
configured and used in three main ways:</p>
+
+<ol>
+<li><p>Via jndi.properties file on the Java Classpath.</p>
+
+<p>By including a file named jndi.properties on the Classpath and setting the
<em>java.naming.factory.initial</em> property
+to value <em>org.apache.qpid.jms.jndi.JmsInitialContextFactory</em>, the Qpid
InitialContextFactory implementation will
+be discovered when instantiating InitialContext object.</p>
+
+<pre><code>javax.naming.Context ctx = new javax.naming.InitialContext();
+</code></pre>
+
+<p>The particular ConnectionFactory, Queue and Topic objects you wish the
context to contain are configured using
+properties (the syntax for which is detailed below) either directly within the
jndi.properties file,
+or in a separate file which is referenced in jndi.properties using the
<em>java.naming.provider.url</em> property.</p></li>
+<li><p>Via system properties.</p>
+
+<p>By setting the <em>java.naming.factory.initial</em> system property to
value <em>org.apache.qpid.jms.jndi.JmsInitialContextFactory</em>,
+the Qpid InitialContextFactory implementation will be discovered when
instantiating InitialContext object.</p>
+
+<pre><code> javax.naming.Context ctx = new javax.naming.InitialContext();
+</code></pre>
+
+<p>The particular ConnectionFactory, Queue and Topic objects you wish the
context to contain are configured as properties in
+a file, which is passed using the <em>java.naming.provider.url</em> system
property. The syntax for these properties is detailed
+below.</p></li>
+<li><p>Programatically using an environment Hashtable.</p>
+
+<p>The InitialContext may also be configured directly by passing an
environment during creation:</p>
+
+<pre><code>Hashtable<Object, Object> env = new Hashtable<Object,
Object>();
+env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.apache.qpid.jms.jndi.JmsInitialContextFactory");
+javax.naming.Context context = new javax.naming.InitialContext(env);
+</code></pre>
+
+<p>The particular ConnectionFactory, Queue and Topic objects you wish the
context to contain are configured as properties
+(the syntax for which is detailed below), either directly within the
environment Hashtable, or in a
+separate file which is referenced using the <em>java.naming.provider.url</em>
property within the environment Hashtable.</p></li>
+</ol>
+
+<p>The property syntax used in the properties file or environment Hashtable is
as follows:</p>
+
+<ul>
+<li>To define a ConnectionFactory, use format:
<em>connectionfactory.lookupName = URI</em></li>
+<li>To define a Queue, use format: <em>queue.lookupName = queueName</em></li>
+<li>To define a Topic use format: <em>topic.lookupName = topicName</em></li>
+</ul>
+
+<p>For more details of the Connection URI, see the next section.</p>
+
+<p>As an example, consider the following properties used to define a
ConnectionFactory, Queue, and Topic:</p>
+
+<pre><code>connectionfactory.myFactoryLookup = amqp://localhost:5672
+queue.myQueueLookup = queueA
+topic.myTopicLookup = topicA
+</code></pre>
+
+<p>These objects could then be looked up from a Context as follows:</p>
+
+<pre><code>ConnectionFactory factory = (ConnectionFactory)
context.lookup("myFactoryLookup");
+Queue queue = (Queue) context.lookup("myQueueLookup");
+Topic topic = (Topic) context.lookup("myTopicLookup");
+</code></pre>
+
+<h2 id="connection-uri">Connection URI</h2>
+
+<p>The basic format of the clients Connection URI is as follows:</p>
+
+<pre><code> amqp://hostname:port[?option=value[&option2=value...]]
+</code></pre>
+
+<p>The client can be configured with a number of different settings using the
URI while defining the ConnectionFactory, these are detailed in the following
sections.</p>
+
+<h3 id="jms-configuration-options">JMS Configuration options</h3>
+
+<p>The options apply to the behaviour of the JMS objects such as Connection,
Session, MessageConsumer and MessageProducer.</p>
+
+<ul>
+<li><strong>jms.username</strong> User name value used to authenticate the
connection</li>
+<li><strong>jms.password</strong> The password value used to authenticate the
connection</li>
+<li><strong>jms.clientID</strong> The ClientID value that is applied to the
connection.</li>
+<li><strong>jms.forceAsyncSend</strong> Configures whether all Messages sent
from a MessageProducer are sent asynchronously or only those Message that
qualify such as Messages inside a transaction or non-persistent messages.</li>
+<li><strong>jms.alwaysSyncSend</strong> Override all asynchronous send
conditions and always sends every Message from a MessageProducer
synchronously.</li>
+<li><strong>jms.sendAcksAsync</strong> Causes all Message acknowledgments to
be sent asynchronously.</li>
+<li><strong>jms.localMessagePriority</strong> If enabled prefetched messages
are reordered locally based on their given Message priority value.</li>
+<li><strong>jms.validatePropertyNames</strong> If message property names
should be validated as valid Java identifiers. Default is true.</li>
+<li><strong>jms.queuePrefix</strong> Optional prefix value added to the name
of any Queue created from a JMS Session.</li>
+<li><strong>jms.topicPrefix</strong> Optional prefix value added to the name
of any Topic created from a JMS Session.</li>
+<li><strong>jms.closeTimeout</strong> Timeout value that controls how long the
client waits on Connection close before returning. (By default the client waits
15 seconds for a normal close completion event).</li>
+<li><strong>jms.connectTimeout</strong> Timeout value that controls how long
the client waits on Connection establishment before returning with an error.
(By default the client waits 15 seconds for a connection to be established
before failing).</li>
+<li><strong>jms.clientIDPrefix</strong> Optional prefix value that is used for
generated Client ID values when a new Connection is created for the JMS
ConnectionFactory. The default prefix is 'ID:'.</li>
+<li><strong>jms.connectionIDPrefix</strong> Optional prefix value that is used
for generated Connection ID values when a new Connection is created for the JMS
ConnectionFactory. This connection ID is used when logging some information
from the JMS Connection object so a configurable prefix can make breadcrumbing
the logs easier. The default prefix is 'ID:'.</li>
+</ul>
+
+<p>These values control how many messages the remote peer can send to the
client and be held in a prefetch buffer for each consumer instance.</p>
+
+<ul>
+<li><strong>jms.prefetchPolicy.queuePrefetch</strong> defaults to 1000</li>
+<li><strong>jms.prefetchPolicy.topicPrefetch</strong> defaults to 1000</li>
+<li><strong>jms.prefetchPolicy.queueBrowserPrefetch</strong> defaults to
1000</li>
+<li><strong>jms.prefetchPolicy.durableTopicPrefetch</strong> defaults to
1000</li>
+<li><strong>jms.prefetchPolicy.all</strong> used to set all prefetch values at
once.</li>
+</ul>
+
+<p>The RedeliveryPolicy controls how redelivered messages are handled on the
client.</p>
+
+<ul>
+<li><strong>jms.redeliveryPolicy.maxRedeliveries</strong> controls when an
incoming message is rejected based on the number of times it has been
redelivered, the default value is (-1) disabled. A value of zero would
indicate no message redeliveries are accepted, a value of five would allow a
message to be redelivered five times, etc.</li>
+</ul>
+
+<h3 id="tcp-transport-configuration-options">TCP Transport Configuration
options</h3>
+
+<p>When connected to a remote using plain TCP these options configure the
behaviour of the underlying socket. These options are appended to the
connection URI along with the other configuration options, for example:</p>
+
+<pre><code>
amqp://localhost:5672?jms.clientID=foo&transport.connectTimeout=30000
+</code></pre>
+
+<p>The complete set of TCP Transport options is listed below:</p>
+
+<ul>
+<li><strong>transport.sendBufferSize</strong> default is 64k</li>
+<li><strong>transport.receiveBufferSize</strong> default is 64k</li>
+<li><strong>transport.trafficClass</strong> default is 0</li>
+<li><strong>transport.connectTimeout</strong> default is 60 seconds</li>
+<li><strong>transport.soTimeout</strong> default is -1</li>
+<li><strong>transport.soLinger</strong> default is -1</li>
+<li><strong>transport.tcpKeepAlive</strong> default is false</li>
+<li><strong>transport.tcpNoDelay</strong> default is true</li>
+</ul>
+
+<h3 id="ssl-transport-configuration-options">SSL Transport Configuration
options</h3>
+
+<p>The SSL Transport extends the TCP Transport and is enabled using the
<em>amqps</em> URI scheme. Because the SSL Transport extends the functionality
of the TCP based Transport all the TCP Transport options are valid on an SSL
Transport URI.</p>
+
+<p>A simple SSL based client URI is shown below:</p>
+
+<pre><code>amqps://localhost:5673
+</code></pre>
+
+<p>The complete set of SSL Transport options is listed below:</p>
+
+<ul>
+<li><strong>transport.keyStoreLocation</strong> default is to read from the
system property "javax.net.ssl.keyStore"</li>
+<li><strong>transport.keyStorePassword</strong> default is to read from the
system property "javax.net.ssl.keyStorePassword"</li>
+<li><strong>transport.trustStoreLocation</strong> default is to read from the
system property "javax.net.ssl.trustStore"</li>
+<li><strong>transport.trustStorePassword</strong> default is to read from the
system property "javax.net.ssl.keyStorePassword"</li>
+<li><strong>transport.storeType</strong> The type of trust store being used.
Default is "JKS".</li>
+<li><strong>transport.contextProtocol</strong> The protocol argument used when
getting an SSLContext. Default is "TLS".</li>
+<li><strong>transport.enabledCipherSuites</strong> The cipher suites to
enable, comma separated. No default, meaning the context default ciphers are
used. Any disabled ciphers are removed from this.</li>
+<li><strong>transport.disabledCipherSuites</strong> The cipher suites to
disable, comma separated. Ciphers listed here are removed from the enabled
ciphers. No default.</li>
+<li><strong>transport.enabledProtocols</strong> The protocols to enable, comma
separated. No default, meaning the context default protocols are used. Any
disabled protocols are removed from this.</li>
+<li><strong>transport.disabledProtocols</strong> The protocols to disable,
comma separated. Protocols listed here are removed from the enabled protocols.
Default is "SSLv2Hello,SSLv3".</li>
+<li><strong>transport.trustAll</strong> Whether to trust the provided server
certificate implicitly, regardless of any configured trust store. Defaults to
false.</li>
+<li><strong>transport.verifyHost</strong> Whether to verify that the hostname
being connected to matches with the provided server certificate. Defaults to
true.</li>
+<li><strong>transport.keyAlias</strong> The alias to use when selecting a
keypair from the keystore if required to send a client certificate to the
server. No default.</li>
+</ul>
+
+<h3 id="failover-configuration-options">Failover Configuration options</h3>
+
+<p>With failover enabled the client can reconnect to a different broker
automatically when the connection to the current connection is lost for some
reason. The failover URI is always initiated with the <em>failover</em> prefix
and a list of URIs for the brokers is contained inside a set of parenthesis.</p>
+
+<p>The URI for failover looks something like the following:</p>
+
+<pre><code>failover:(amqp://broker1:5672,amqp://broker2:5672)?failover.maxReconnectAttempts=20
+</code></pre>
+
+<p>The complete set of configuration options for failover is listed below:</p>
+
+<ul>
+<li><strong>failover.initialReconnectDelay</strong> The amount of time the
client will wait before the first attempt to reconnect to a remote peer. The
default value is zero, meaning the first attempt happens immediately.</li>
+<li><strong>failover.reconnectDelay</strong> Controls the delay between
successive reconnection attempts, defaults to 10 milliseconds. If the backoff
option is not enabled this value remains constant.</li>
+<li><strong>failover.maxReconnectDelay</strong> The maximum time that the
client will wait before attempting a reconnect. This value is only used when
the backoff feature is enabled to ensure that the delay doesn't not grow too
large. Defaults to 30 seconds as the max time between connect attempts.</li>
+<li><strong>failover.useReconnectBackOff</strong> Controls whether the time
between reconnection attempts should grow based on a configured multiplier.
This option defaults to true.</li>
+<li><strong>failover.reconnectBackOffMultiplier</strong> The multiplier used
to grow the reconnection delay value, defaults to 2.0d.</li>
+<li><strong>failover.maxReconnectAttempts</strong> The number of reconnection
attempts allowed before reporting the connection as failed to the client. The
default is no limit or (-1).</li>
+<li><strong>failover.startupMaxReconnectAttempts</strong> For a client that
has never connected to a remote peer before this option control how many
attempts are made to connect before reporting the connection as failed. The
default is to use the value of maxReconnectAttempts.</li>
+<li><strong>failover.warnAfterReconnectAttempts</strong> Controls how often
the client will log a message indicating that failover reconnection is being
attempted. The default is to log every 10 connection attempts.</li>
+</ul>
+
+<p>The failover URI options also supports defining 'nested' options applicable
to each individual broker URI, which can be used to avoid repetition and define
options common to them all. This is accomplished using the same URI options
outlined earlier for the indivual broker URI but now prefixed with
<em>failover.nested.</em>:</p>
+
+<pre><code>failover:(amqp://broker1:5672,amqp://broker2:5672)?failover.nested.jms.clientID=foo
+</code></pre>
+
+<h3 id="amqp-configuration-options">AMQP Configuration options</h3>
+
+<p>These options apply to the behaviour of certain AMQP functionality.</p>
+
+<ul>
+<li><strong>amqp.idleTimeout</strong> The idle timeout in milliseconds after
which the connection will be failed if the peer sends no AMQP frames. Default
is 60000.</li>
+<li><strong>amqp.vhost</strong> The vhost to connect to. Used to populate the
Sasl and Open hostname fields. Default is the main hostname from the Connection
URI.</li>
+</ul>
+
+<h3 id="discovery-configuration-options">Discovery Configuration options</h3>
+
+<p>The client has an optional Discovery module, which provides a customised
failover layer where the broker URIs to connect to are not given in the initial
URI, but discovered as the client operates via associated discovery agents.
There are currently two discovery agent implementations, a file watcher that
loads URIs from a file, and a multicast listener that works with ActiveMQ 5
brokers which have been configured to broadcast their broker addresses for
listening clients.</p>
+
+<p>The general set of failover related options when using discovery are the
same as those detailed earlier, with the main prefix updated from
<em>failover.</em> to <em>discovery.</em>, and with the 'nested' options prefix
used to supply URI options common to all the discovered broker URIs bring
updated from <em>failover.nested.</em> to <em>discovery.discovered</em>. For
example, without the agent URI details, a general discovery URI might look
like:</p>
+
+<pre><code>discovery:(<agent-uri>)?discovery.maxReconnectAttempts=20&discovery.discovered.jms.clientID=foo
+</code></pre>
+
+<p>To use the file watcher discovery agent, utilise an agent URI of the
form:</p>
+
+<pre><code>discovery:(file:///path/to/monitored-file?updateInterval=60000)
+</code></pre>
+
+<p>The URI options for the file watcher discovery agent are listed below:</p>
+
+<ul>
+<li><strong>updateInterval</strong> Controls the frequency in milliseconds
which the file is inspected for change. The default value is 30000.</li>
+</ul>
+
+<p>To use the multicast discovery agent with an ActiveMQ 5 broker, utilise an
agent URI of the form:</p>
+
+<pre><code>discovery:(multicast://default?group=default)
+</code></pre>
+
+<p>Note that the use of <em>default</em> as the host in the multicast agent
URI above is a special value (that is substituted by the agent with the default
"239.255.2.3:6155"). You may change this to specify the actual IP and port in
use with your multicast configuration.</p>
+
+<p>The URI options for the multicast discovery agent are listed below:</p>
+
+<ul>
+<li><strong>group</strong> Controls which multicast group messages are
listened for on. The default value is "default".</li>
+</ul>
+
+<h2 id="logging">Logging</h2>
+
+<p>The client makes use of the SLF4J API, allowing users to select a
particular logging implementation based on their needs by supplying a SLF4J
'binding', such as <em>slf4j-log4j</em> in order to use Log4J. More details on
SLF4J are available from http://www.slf4j.org/.</p>
+
+<p>The client uses Logger names residing within the
<em>org.apache.qpid.jms</em> heirarchy, which you can use to configure a
logging implementation based on your needs.</p>
+
+<p>When debugging some issues, it may sometimes be useful to enable additional
protocol trace logging from the Qpid Proton AMQP 1.0 library. There are two
options to achieve this:</p>
+
+<ul>
+<li>Set the environment variable (not Java system property)
<em>PN_TRACE_FRM</em> to <em>true</em>, which will cause Proton to emit frame
logging to stdout.</li>
+<li>Add the option <em>amqp.traceFrames=true</em> to your connection URI to
have the client add a protocol tracer to Proton, and configure the
<em>org.apache.qpid.jms.provider.amqp.FRAMES</em> Logger to <em>TRACE</em>
level to include the output in your logs.</li>
+</ul>
+
+
+ <hr/>
+
+ <ul id="-apache-navigation">
+ <li><a href="http://www.apache.org/";>Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/";>License</a></li>
+ <li><a
href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li>
+ <li><a
href="http://www.apache.org/foundation/thanks.html";>Thanks!</a></li>
+ <li><a href="http://www.apache.org/security/";>Security</a></li>
+ <li><a href="http://www.apache.org/";><img id="-apache-feather"
width="48" height="14" src="data:image/png;base64," alt="Apache"/></a></li>
+ </ul>
+
+ <p id="-legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2013
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache
+ License, Version 2.0</a>; Apache Qpid, Qpid, Qpid Proton,
+ Proton, Apache, the Apache feather logo, and the Apache Qpid
+ project logo are trademarks of The Apache Software
+ Foundation; All other marks mentioned may be trademarks or
+ registered trademarks of their respective owners
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Copied: qpid/site/docs/releases/qpid-jms-0.3.0/index.html (from r1683498,
qpid/site/docs/releases/qpid-jms-0.2.0/index.html)
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-jms-0.3.0/index.html?p2=qpid/site/docs/releases/qpid-jms-0.3.0/index.html&p1=qpid/site/docs/releases/qpid-jms-0.2.0/index.html&r1=1683498&r2=1685611&rev=1685611&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-jms-0.2.0/index.html (original)
+++ qpid/site/docs/releases/qpid-jms-0.3.0/index.html Mon Jun 15 16:04:54 2015
@@ -21,7 +21,7 @@
-->
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Qpid JMS 0.2.0 - Apache Qpid™</title>
+ <title>Qpid JMS 0.3.0 - Apache Qpid™</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
@@ -102,16 +102,16 @@
</div>
<div id="-middle" class="panel">
- <ul id="-path-navigation"><li><a
href="/index.html">Home</a></li><li><a
href="/releases/index.html">Releases</a></li><li>Qpid JMS 0.2.0</li></ul>
+ <ul id="-path-navigation"><li><a
href="/index.html">Home</a></li><li><a
href="/releases/index.html">Releases</a></li><li>Qpid JMS 0.3.0</li></ul>
<script type="text/javascript">
_deferredFunctions.push(function() {
- if ("0.2.0" === "0.2.0") {
+ if ("0.3.0" === "0.3.0") {
_modifyCurrentReleaseLinks();
}
});
</script>
-<h1 id="qpid-jms-020">Qpid JMS 0.2.0</h1>
+<h1 id="qpid-jms-030">Qpid JMS 0.3.0</h1>
<p>Qpid JMS is a complete <a
href="http://en.wikipedia.org/wiki/Java_Message_Service";>Java Message
Service</a> 1.1 client built
using the <a href="/proton/index.html">Qpid Proton</a> protocol engine.</p>
@@ -128,8 +128,8 @@ files you download.</p>
<table>
<tbody>
<tr><td><em>Content</em></td><td><em>Download</em></td><td><em>Verify</em></td></tr>
-<tr><td>Qpid JMS binaries</td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz";>apache-qpid-jms-0.2.0-bin.tar.gz</a></td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.asc";>ASC</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.md5";>MD5</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.sha1";>SHA1</a></td></tr>
-<tr><td>Qpid JMS source code</td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz";>apache-qpid-jms-0.2.0-src.tar.gz</a></td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.asc";>ASC</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.md5";>MD5</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.sha1";>SHA1</a></td></tr>
+<tr><td>Qpid JMS binaries</td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz";>apache-qpid-jms-0.3.0-bin.tar.gz</a></td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.asc";>ASC</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.md5";>MD5</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.sha1";>SHA1</a></td></tr>
+<tr><td>Qpid JMS source code</td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz";>apache-qpid-jms-0.3.0-src.tar.gz</a></td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.asc";>ASC</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.md5";>MD5</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.sha1";>SHA1</a></td></tr>
</tbody>
</table>
@@ -141,7 +141,7 @@ files you download.</p>
<ul>
<li><a
href="http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html";>API
reference</a></li>
-<li><a
href="https://github.com/apache/qpid-jms/tree/0.2.0/qpid-jms-examples";>Examples</a></li>
+<li><a
href="https://github.com/apache/qpid-jms/tree/0.3.0/qpid-jms-examples";>Examples</a></li>
<li><a href="docs/index.html">Configuration</a></li>
<li><a href="building.html">Building Qpid JMS</a></li>
</ul>
@@ -151,9 +151,9 @@ files you download.</p>
<h2 id="more-information">More information</h2>
<ul>
-<li><a href="http://archive.apache.org/dist/qpid/jms/0.2.0";>All release
artefacts</a></li>
-<li><a
href="https://issues.apache.org/jira/issues/?jql=project+%3D+QPIDJMS+AND+fixVersion+%3D+%270.2.0%27+ORDER+BY+priority+DESC";>Resolved
issues in JIRA</a></li>
-<li><a
href="https://git-wip-us.apache.org/repos/asf/qpid-jms.git/tree/refs/tags/0.2.0";>Source
repository tag</a></li>
+<li><a href="http://archive.apache.org/dist/qpid/jms/0.3.0";>All release
artefacts</a></li>
+<li><a
href="https://issues.apache.org/jira/issues/?jql=project+%3D+QPIDJMS+AND+fixVersion+%3D+%270.3.0%27+ORDER+BY+priority+DESC";>Resolved
issues in JIRA</a></li>
+<li><a
href="https://git-wip-us.apache.org/repos/asf/qpid-jms.git/tree/refs/tags/0.3.0";>Source
repository tag</a></li>
</ul>
Copied: qpid/site/docs/releases/qpid-jms-0.3.0/release-notes.html (from
r1683498, qpid/site/docs/releases/qpid-jms-0.2.0/index.html)
URL:
http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-jms-0.3.0/release-notes.html?p2=qpid/site/docs/releases/qpid-jms-0.3.0/release-notes.html&p1=qpid/site/docs/releases/qpid-jms-0.2.0/index.html&r1=1683498&r2=1685611&rev=1685611&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-jms-0.2.0/index.html (original)
+++ qpid/site/docs/releases/qpid-jms-0.3.0/release-notes.html Mon Jun 15
16:04:54 2015
@@ -21,7 +21,7 @@
-->
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Qpid JMS 0.2.0 - Apache Qpid™</title>
+ <title>Qpid JMS 0.3.0 Release Notes - Apache Qpid™</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
@@ -102,58 +102,44 @@
</div>
<div id="-middle" class="panel">
- <ul id="-path-navigation"><li><a
href="/index.html">Home</a></li><li><a
href="/releases/index.html">Releases</a></li><li>Qpid JMS 0.2.0</li></ul>
- <script type="text/javascript">
- _deferredFunctions.push(function() {
- if ("0.2.0" === "0.2.0") {
- _modifyCurrentReleaseLinks();
- }
- });
-</script>
-
-<h1 id="qpid-jms-020">Qpid JMS 0.2.0</h1>
+ <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-jms-0.3.0/index.html">Qpid JMS 0.3.0</a></li><li>Qpid JMS
0.3.0 Release Notes</li></ul>
+ <h1 id="qpid-jms-030-release-notes">Qpid JMS 0.3.0 Release Notes</h1>
<p>Qpid JMS is a complete <a
href="http://en.wikipedia.org/wiki/Java_Message_Service";>Java Message
Service</a> 1.1 client built
using the <a href="/proton/index.html">Qpid Proton</a> protocol engine.</p>
-<p>For a detailed list of the changes in this release, see the <a
href="release-notes.html">release
-notes</a>.</p>
-
-<h2 id="download">Download</h2>
-
-<p>It's important to <a href="/download.html#verify-what-you-download">verify
the
-integrity</a> of the
-files you download.</p>
-
-<table>
-<tbody>
-<tr><td><em>Content</em></td><td><em>Download</em></td><td><em>Verify</em></td></tr>
-<tr><td>Qpid JMS binaries</td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz";>apache-qpid-jms-0.2.0-bin.tar.gz</a></td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.asc";>ASC</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.md5";>MD5</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-bin.tar.gz.sha1";>SHA1</a></td></tr>
-<tr><td>Qpid JMS source code</td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz";>apache-qpid-jms-0.2.0-src.tar.gz</a></td><td><a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.asc";>ASC</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.md5";>MD5</a>,
<a
href="http://archive.apache.org/dist/qpid/jms/0.2.0/apache-qpid-jms-0.2.0-src.tar.gz.sha1";>SHA1</a></td></tr>
-</tbody>
-</table>
+<p>For more information about this release, including download links and
+documentation, see the <a href="index.html">release overview</a>.</p>
-<p>The client is also available <a href="/maven.html">via Maven</a>.</p>
-
-<h2 id="documentation">Documentation</h2>
-
-<div class="two-column">
+<h2 id="new-features-and-improvements">New features and improvements</h2>
<ul>
-<li><a
href="http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html";>API
reference</a></li>
-<li><a
href="https://github.com/apache/qpid-jms/tree/0.2.0/qpid-jms-examples";>Examples</a></li>
-<li><a href="docs/index.html">Configuration</a></li>
-<li><a href="building.html">Building Qpid JMS</a></li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-53";>QPIDJMS-53</a>
- treat messages with a Data section and common textual content-type values as
TextMessage</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-55";>QPIDJMS-55</a>
- Add support for using standard AMQP ports if the URI fails to provide one</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-61";>QPIDJMS-61</a>
- add support for setting the sasl / open frame 'hostname'</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-64";>QPIDJMS-64</a>
- Throw a JMSException with a more consistent error message when connection
attempts fail</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-70";>QPIDJMS-70</a>
- Add a redelivery policy to control when the client should reject new
deliveries based on the delivery count.</li>
</ul>
-</div>
-
-<h2 id="more-information">More information</h2>
+<h2 id="bugs-fixed">Bugs fixed</h2>
<ul>
-<li><a href="http://archive.apache.org/dist/qpid/jms/0.2.0";>All release
artefacts</a></li>
-<li><a
href="https://issues.apache.org/jira/issues/?jql=project+%3D+QPIDJMS+AND+fixVersion+%3D+%270.2.0%27+ORDER+BY+priority+DESC";>Resolved
issues in JIRA</a></li>
-<li><a
href="https://git-wip-us.apache.org/repos/asf/qpid-jms.git/tree/refs/tags/0.2.0";>Source
repository tag</a></li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-48";>QPIDJMS-48</a>
- inconsistent handling of property names in Message methods</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-49";>QPIDJMS-49</a>
- handle messages with an unknown content-type</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-52";>QPIDJMS-52</a>
- support charset parameter in content-type value</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-54";>QPIDJMS-54</a>
- remove extraneous indirection around selector verification</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-56";>QPIDJMS-56</a>
- throw InvalidClientIDException rather than JMSException when hint present
that container-id was the problem field</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-57";>QPIDJMS-57</a>
- ErrorCondition 'info' field lookups should use Symbol keys</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-58";>QPIDJMS-58</a>
- when a connection redirect error is received, the original connection details
will be used first</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-59";>QPIDJMS-59</a>
- uri pool object is not thread safe but is accessed by multiple threads</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-60";>QPIDJMS-60</a>
- using 'nested options' causes issues when adding/removing a URI from the pool
object</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-62";>QPIDJMS-62</a>
- ensure that a body section is always sent when using ObjectMessage</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-63";>QPIDJMS-63</a>
- SASL ANONYMOUS doesn't seem to work against the C++ broker</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-65";>QPIDJMS-65</a>
- updated SASL mechanism selection to consider available credentials</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-66";>QPIDJMS-66</a>
- fix documentation of URI option for ClientID</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-67";>QPIDJMS-67</a>
- AMQP header and Open+Close frames are sent after a SASL failure</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-71";>QPIDJMS-71</a>
- calling receive(0) on a consumer always returns null</li>
+<li><a href="https://issues.apache.org/jira/browse/QPIDJMS-72";>QPIDJMS-72</a>
- update discovery uri syntax for consistency and add some basic
documentation</li>
</ul>
Modified: qpid/site/input/_config.ini
URL:
http://svn.apache.org/viewvc/qpid/site/input/_config.ini?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/input/_config.ini (original)
+++ qpid/site/input/_config.ini Mon Jun 15 16:04:54 2015
@@ -3,7 +3,7 @@ current-release = 0.32
current-release-url = %(site-url)s/releases/qpid-%(current-release)s
current-release-link = <a href="%(current-release-url)s/index.html">Qpid
%(current-release)s</a>
current-release-tag =
http://svn.apache.org/repos/asf/qpid/tags/%(current-release)s
-current-jms-release = 0.2.0
+current-jms-release = 0.3.0
current-jms-release-url =
%(site-url)s/releases/qpid-jms-%(current-jms-release)s
current-jms-release-link = <a
href="%(current-jms-release-url)s/index.html">Qpid JMS
%(current-jms-release)s</a>
current-proton-release = 0.9.1
Modified: qpid/site/input/releases/index.md
URL:
http://svn.apache.org/viewvc/qpid/site/input/releases/index.md?rev=1685611&r1=1685610&r2=1685611&view=diff
==============================================================================
--- qpid/site/input/releases/index.md (original)
+++ qpid/site/input/releases/index.md Mon Jun 15 16:04:54 2015
@@ -27,13 +27,14 @@ and the
## Current releases
- - [Qpid JMS 0.2.0](qpid-jms-0.2.0/index.html), May 2015
+ - [Qpid JMS 0.3.0](qpid-jms-0.3.0/index.html), June 2015
- [Qpid 0.32](qpid-0.32/index.html), March 2015
- [Qpid Dispatch 0.4](qpid-dispatch-0.4/index.html), April 2015
- [Qpid Proton 0.9.1](qpid-proton-0.9.1/index.html), May 2015
## Past releases
+ - [Qpid JMS 0.2.0](qpid-jms-0.2.0/index.html), May 2015
- [Qpid JMS 0.1.0](qpid-jms-0.1.0/index.html), March 2015
- [Qpid Proton 0.9](qpid-proton-0.9/index.html), March 2015
- [Qpid Dispatch 0.3](qpid-dispatch-0.3/index.html), January 2015
Added: qpid/site/input/releases/qpid-jms-0.3.0/building.md
URL:
http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-jms-0.3.0/building.md?rev=1685611&view=auto
==============================================================================
--- qpid/site/input/releases/qpid-jms-0.3.0/building.md (added)
+++ qpid/site/input/releases/qpid-jms-0.3.0/building.md Mon Jun 15 16:04:54 2015
@@ -0,0 +1,43 @@
+# QpidJMS
+
+The QpidJMS project provides a JMS based client that uses the AMQP v1.0
protocol.
+
+Below are some quick pointers you might find useful.
+
+## Building the code
+
+The project requires Maven 3. Some example commands follow.
+
+Clean previous builds output and install all modules to local repository
without
+running the tests:
+
+ mvn clean install -DskipTests
+
+Install all modules to the local repository after running all the tests:
+
+ mvn clean install
+
+Perform a subset tests on the packaged release artifacts without
+installing:
+
+ mvn clean verify -Dtest=TestNamePattern*
+
+Execute the tests and produce code coverage report:
+
+ mvn clean test jacoco:report
+
+## Examples
+
+First build and install all the modules as detailed above (if running against
+a source checkout/release, rather than against released binaries) and then
+consult the README in the qpid-jms-examples module itself.
+
+## Documentation
+
+There is some basic documentation in the qpid-jms-docs module.
+
+## Distribution assemblies
+
+After building the modules, src and binary distribution assemblies can be
found at:
+
+ apache-qpid-jms/target
Added: qpid/site/input/releases/qpid-jms-0.3.0/docs/index.md
URL:
http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-jms-0.3.0/docs/index.md?rev=1685611&view=auto
==============================================================================
--- qpid/site/input/releases/qpid-jms-0.3.0/docs/index.md (added)
+++ qpid/site/input/releases/qpid-jms-0.3.0/docs/index.md Mon Jun 15 16:04:54
2015
@@ -0,0 +1,213 @@
+# Client configuration
+
+This file details various configuration options for the client, such as how to
configure and create a JNDI InitialContext, the syntax for its related
configuration, and various URI options that can be set when defining a
ConnectionFactory.
+
+## Configuring a JNDI InitialContext
+
+Applications use a JNDI InitialContext, itself obtained from an
InitialContextFactory, to look up JMS objects such as ConnectionFactory. The
Qpid JMS client provides an implementation of the InitialContextFactory in
class *org.apache.qpid.jms.jndi.JmsInitialContextFactory*. This may be
configured and used in three main ways:
+
+1. Via jndi.properties file on the Java Classpath.
+
+ By including a file named jndi.properties on the Classpath and setting the
*java.naming.factory.initial* property
+ to value *org.apache.qpid.jms.jndi.JmsInitialContextFactory*, the Qpid
InitialContextFactory implementation will
+ be discovered when instantiating InitialContext object.
+
+ javax.naming.Context ctx = new javax.naming.InitialContext();
+
+ The particular ConnectionFactory, Queue and Topic objects you wish the
context to contain are configured using
+ properties (the syntax for which is detailed below) either directly within
the jndi.properties file,
+ or in a separate file which is referenced in jndi.properties using the
*java.naming.provider.url* property.
+
+2. Via system properties.
+
+ By setting the *java.naming.factory.initial* system property to value
*org.apache.qpid.jms.jndi.JmsInitialContextFactory*,
+ the Qpid InitialContextFactory implementation will be discovered when
instantiating InitialContext object.
+
+ javax.naming.Context ctx = new javax.naming.InitialContext();
+
+ The particular ConnectionFactory, Queue and Topic objects you wish the
context to contain are configured as properties in
+ a file, which is passed using the *java.naming.provider.url* system
property. The syntax for these properties is detailed
+ below.
+
+3. Programatically using an environment Hashtable.
+
+ The InitialContext may also be configured directly by passing an
environment during creation:
+
+ Hashtable<Object, Object> env = new Hashtable<Object, Object>();
+ env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.apache.qpid.jms.jndi.JmsInitialContextFactory");
+ javax.naming.Context context = new javax.naming.InitialContext(env);
+
+ The particular ConnectionFactory, Queue and Topic objects you wish the
context to contain are configured as properties
+ (the syntax for which is detailed below), either directly within the
environment Hashtable, or in a
+ separate file which is referenced using the *java.naming.provider.url*
property within the environment Hashtable.
+
+The property syntax used in the properties file or environment Hashtable is as
follows:
+
++ To define a ConnectionFactory, use format: *connectionfactory.lookupName =
URI*
++ To define a Queue, use format: *queue.lookupName = queueName*
++ To define a Topic use format: *topic.lookupName = topicName*
+
+For more details of the Connection URI, see the next section.
+
+As an example, consider the following properties used to define a
ConnectionFactory, Queue, and Topic:
+
+ connectionfactory.myFactoryLookup = amqp://localhost:5672
+ queue.myQueueLookup = queueA
+ topic.myTopicLookup = topicA
+
+These objects could then be looked up from a Context as follows:
+
+ ConnectionFactory factory = (ConnectionFactory)
context.lookup("myFactoryLookup");
+ Queue queue = (Queue) context.lookup("myQueueLookup");
+ Topic topic = (Topic) context.lookup("myTopicLookup");
+
+## Connection URI
+
+The basic format of the clients Connection URI is as follows:
+
+ amqp://hostname:port[?option=value[&option2=value...]]
+
+The client can be configured with a number of different settings using the URI
while defining the ConnectionFactory, these are detailed in the following
sections.
+
+### JMS Configuration options
+
+The options apply to the behaviour of the JMS objects such as Connection,
Session, MessageConsumer and MessageProducer.
+
++ **jms.username** User name value used to authenticate the connection
++ **jms.password** The password value used to authenticate the connection
++ **jms.clientID** The ClientID value that is applied to the connection.
++ **jms.forceAsyncSend** Configures whether all Messages sent from a
MessageProducer are sent asynchronously or only those Message that qualify such
as Messages inside a transaction or non-persistent messages.
++ **jms.alwaysSyncSend** Override all asynchronous send conditions and always
sends every Message from a MessageProducer synchronously.
++ **jms.sendAcksAsync** Causes all Message acknowledgments to be sent
asynchronously.
++ **jms.localMessagePriority** If enabled prefetched messages are reordered
locally based on their given Message priority value.
++ **jms.validatePropertyNames** If message property names should be validated
as valid Java identifiers. Default is true.
++ **jms.queuePrefix** Optional prefix value added to the name of any Queue
created from a JMS Session.
++ **jms.topicPrefix** Optional prefix value added to the name of any Topic
created from a JMS Session.
++ **jms.closeTimeout** Timeout value that controls how long the client waits
on Connection close before returning. (By default the client waits 15 seconds
for a normal close completion event).
++ **jms.connectTimeout** Timeout value that controls how long the client waits
on Connection establishment before returning with an error. (By default the
client waits 15 seconds for a connection to be established before failing).
++ **jms.clientIDPrefix** Optional prefix value that is used for generated
Client ID values when a new Connection is created for the JMS
ConnectionFactory. The default prefix is 'ID:'.
++ **jms.connectionIDPrefix** Optional prefix value that is used for generated
Connection ID values when a new Connection is created for the JMS
ConnectionFactory. This connection ID is used when logging some information
from the JMS Connection object so a configurable prefix can make breadcrumbing
the logs easier. The default prefix is 'ID:'.
+
+These values control how many messages the remote peer can send to the client
and be held in a prefetch buffer for each consumer instance.
+
++ **jms.prefetchPolicy.queuePrefetch** defaults to 1000
++ **jms.prefetchPolicy.topicPrefetch** defaults to 1000
++ **jms.prefetchPolicy.queueBrowserPrefetch** defaults to 1000
++ **jms.prefetchPolicy.durableTopicPrefetch** defaults to 1000
++ **jms.prefetchPolicy.all** used to set all prefetch values at once.
+
+The RedeliveryPolicy controls how redelivered messages are handled on the
client.
+
++ **jms.redeliveryPolicy.maxRedeliveries** controls when an incoming message
is rejected based on the number of times it has been redelivered, the default
value is (-1) disabled. A value of zero would indicate no message redeliveries
are accepted, a value of five would allow a message to be redelivered five
times, etc.
+
+### TCP Transport Configuration options
+
+When connected to a remote using plain TCP these options configure the
behaviour of the underlying socket. These options are appended to the
connection URI along with the other configuration options, for example:
+
+ amqp://localhost:5672?jms.clientID=foo&transport.connectTimeout=30000
+
+The complete set of TCP Transport options is listed below:
+
++ **transport.sendBufferSize** default is 64k
++ **transport.receiveBufferSize** default is 64k
++ **transport.trafficClass** default is 0
++ **transport.connectTimeout** default is 60 seconds
++ **transport.soTimeout** default is -1
++ **transport.soLinger** default is -1
++ **transport.tcpKeepAlive** default is false
++ **transport.tcpNoDelay** default is true
+
+### SSL Transport Configuration options
+
+The SSL Transport extends the TCP Transport and is enabled using the *amqps*
URI scheme. Because the SSL Transport extends the functionality of the TCP
based Transport all the TCP Transport options are valid on an SSL Transport URI.
+
+A simple SSL based client URI is shown below:
+
+ amqps://localhost:5673
+
+The complete set of SSL Transport options is listed below:
+
++ **transport.keyStoreLocation** default is to read from the system property
"javax.net.ssl.keyStore"
++ **transport.keyStorePassword** default is to read from the system property
"javax.net.ssl.keyStorePassword"
++ **transport.trustStoreLocation** default is to read from the system
property "javax.net.ssl.trustStore"
++ **transport.trustStorePassword** default is to read from the system
property "javax.net.ssl.keyStorePassword"
++ **transport.storeType** The type of trust store being used. Default is "JKS".
++ **transport.contextProtocol** The protocol argument used when getting an
SSLContext. Default is "TLS".
++ **transport.enabledCipherSuites** The cipher suites to enable, comma
separated. No default, meaning the context default ciphers are used. Any
disabled ciphers are removed from this.
++ **transport.disabledCipherSuites** The cipher suites to disable, comma
separated. Ciphers listed here are removed from the enabled ciphers. No default.
++ **transport.enabledProtocols** The protocols to enable, comma separated. No
default, meaning the context default protocols are used. Any disabled protocols
are removed from this.
++ **transport.disabledProtocols** The protocols to disable, comma separated.
Protocols listed here are removed from the enabled protocols. Default is
"SSLv2Hello,SSLv3".
++ **transport.trustAll** Whether to trust the provided server certificate
implicitly, regardless of any configured trust store. Defaults to false.
++ **transport.verifyHost** Whether to verify that the hostname being connected
to matches with the provided server certificate. Defaults to true.
++ **transport.keyAlias** The alias to use when selecting a keypair from the
keystore if required to send a client certificate to the server. No default.
+
+### Failover Configuration options
+
+With failover enabled the client can reconnect to a different broker
automatically when the connection to the current connection is lost for some
reason. The failover URI is always initiated with the *failover* prefix and a
list of URIs for the brokers is contained inside a set of parenthesis.
+
+The URI for failover looks something like the following:
+
+
failover:(amqp://broker1:5672,amqp://broker2:5672)?failover.maxReconnectAttempts=20
+
+The complete set of configuration options for failover is listed below:
+
++ **failover.initialReconnectDelay** The amount of time the client will wait
before the first attempt to reconnect to a remote peer. The default value is
zero, meaning the first attempt happens immediately.
++ **failover.reconnectDelay** Controls the delay between successive
reconnection attempts, defaults to 10 milliseconds. If the backoff option is
not enabled this value remains constant.
++ **failover.maxReconnectDelay** The maximum time that the client will wait
before attempting a reconnect. This value is only used when the backoff
feature is enabled to ensure that the delay doesn't not grow too large.
Defaults to 30 seconds as the max time between connect attempts.
++ **failover.useReconnectBackOff** Controls whether the time between
reconnection attempts should grow based on a configured multiplier. This
option defaults to true.
++ **failover.reconnectBackOffMultiplier** The multiplier used to grow the
reconnection delay value, defaults to 2.0d.
++ **failover.maxReconnectAttempts** The number of reconnection attempts
allowed before reporting the connection as failed to the client. The default
is no limit or (-1).
++ **failover.startupMaxReconnectAttempts** For a client that has never
connected to a remote peer before this option control how many attempts are
made to connect before reporting the connection as failed. The default is to
use the value of maxReconnectAttempts.
++ **failover.warnAfterReconnectAttempts** Controls how often the client will
log a message indicating that failover reconnection is being attempted. The
default is to log every 10 connection attempts.
+
+The failover URI options also supports defining 'nested' options applicable to
each individual broker URI, which can be used to avoid repetition and define
options common to them all. This is accomplished using the same URI options
outlined earlier for the indivual broker URI but now prefixed with
*failover.nested.*:
+
+
failover:(amqp://broker1:5672,amqp://broker2:5672)?failover.nested.jms.clientID=foo
+
+
+### AMQP Configuration options
+
+These options apply to the behaviour of certain AMQP functionality.
+
++ **amqp.idleTimeout** The idle timeout in milliseconds after which the
connection will be failed if the peer sends no AMQP frames. Default is 60000.
++ **amqp.vhost** The vhost to connect to. Used to populate the Sasl and Open
hostname fields. Default is the main hostname from the Connection URI.
+
+
+### Discovery Configuration options
+
+The client has an optional Discovery module, which provides a customised
failover layer where the broker URIs to connect to are not given in the initial
URI, but discovered as the client operates via associated discovery agents.
There are currently two discovery agent implementations, a file watcher that
loads URIs from a file, and a multicast listener that works with ActiveMQ 5
brokers which have been configured to broadcast their broker addresses for
listening clients.
+
+The general set of failover related options when using discovery are the same
as those detailed earlier, with the main prefix updated from *failover.* to
*discovery.*, and with the 'nested' options prefix used to supply URI options
common to all the discovered broker URIs bring updated from *failover.nested.*
to *discovery.discovered*. For example, without the agent URI details, a
general discovery URI might look like:
+
+
discovery:(<agent-uri>)?discovery.maxReconnectAttempts=20&discovery.discovered.jms.clientID=foo
+
+To use the file watcher discovery agent, utilise an agent URI of the form:
+
+ discovery:(file:///path/to/monitored-file?updateInterval=60000)
+
+The URI options for the file watcher discovery agent are listed below:
+
++ **updateInterval** Controls the frequency in milliseconds which the file is
inspected for change. The default value is 30000.
+
+
+To use the multicast discovery agent with an ActiveMQ 5 broker, utilise an
agent URI of the form:
+
+ discovery:(multicast://default?group=default)
+
+Note that the use of *default* as the host in the multicast agent URI above is
a special value (that is substituted by the agent with the default
"239.255.2.3:6155"). You may change this to specify the actual IP and port in
use with your multicast configuration.
+
+The URI options for the multicast discovery agent are listed below:
+
++ **group** Controls which multicast group messages are listened for on. The
default value is "default".
+
+
+## Logging
+
+The client makes use of the SLF4J API, allowing users to select a particular
logging implementation based on their needs by supplying a SLF4J 'binding',
such as *slf4j-log4j* in order to use Log4J. More details on SLF4J are
available from http://www.slf4j.org/.
+
+The client uses Logger names residing within the *org.apache.qpid.jms*
heirarchy, which you can use to configure a logging implementation based on
your needs.
+
+When debugging some issues, it may sometimes be useful to enable additional
protocol trace logging from the Qpid Proton AMQP 1.0 library. There are two
options to achieve this:
+
++ Set the environment variable (not Java system property) *PN_TRACE_FRM* to
*true*, which will cause Proton to emit frame logging to stdout.
++ Add the option *amqp.traceFrames=true* to your connection URI to have the
client add a protocol tracer to Proton, and configure the
*org.apache.qpid.jms.provider.amqp.FRAMES* Logger to *TRACE* level to include
the output in your logs.
Added: qpid/site/input/releases/qpid-jms-0.3.0/index.md
URL:
http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-jms-0.3.0/index.md?rev=1685611&view=auto
==============================================================================
--- qpid/site/input/releases/qpid-jms-0.3.0/index.md (added)
+++ qpid/site/input/releases/qpid-jms-0.3.0/index.md Mon Jun 15 16:04:54 2015
@@ -0,0 +1,64 @@
+;;
+;; Licensed to the Apache Software Foundation (ASF) under one
+;; or more contributor license agreements. See the NOTICE file
+;; distributed with this work for additional information
+;; regarding copyright ownership. The ASF licenses this file
+;; to you under the Apache License, Version 2.0 (the
+;; "License"); you may not use this file except in compliance
+;; with the License. You may obtain a copy of the License at
+;;
+;; http://www.apache.org/licenses/LICENSE-2.0
+;;
+;; Unless required by applicable law or agreed to in writing,
+;; software distributed under the License is distributed on an
+;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+;; KIND, either express or implied. See the License for the
+;; specific language governing permissions and limitations
+;; under the License.
+;;
+
+<script type="text/javascript">
+ _deferredFunctions.push(function() {
+ if ("0.3.0" === "@current-jms-release@") {
+ _modifyCurrentReleaseLinks();
+ }
+ });
+</script>
+
+# Qpid JMS 0.3.0
+
+Qpid JMS is a complete [Java Message Service][jms] 1.1 client built
+using the [Qpid Proton](@site-url@/proton/index.html) protocol engine.
+
+For a detailed list of the changes in this release, see the [release
+notes](release-notes.html).
+
+[jms]: http://en.wikipedia.org/wiki/Java_Message_Service
+
+## Download
+
+It's important to [verify the
+integrity](@site-url@/download.html#verify-what-you-download) of the
+files you download.
+
+ || *Content* || *Download* || *Verify* ||
+ || Qpid JMS binaries ||
[apache-qpid-jms-0.3.0-bin.tar.gz](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz)
||
[ASC](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.asc),
[MD5](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.md5),
[SHA1](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-bin.tar.gz.sha1)
||
+ || Qpid JMS source code ||
[apache-qpid-jms-0.3.0-src.tar.gz](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz)
||
[ASC](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.asc),
[MD5](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.md5),
[SHA1](http://archive.apache.org/dist/qpid/jms/0.3.0/apache-qpid-jms-0.3.0-src.tar.gz.sha1)
||
+
+The client is also available [via Maven](@site-url@/maven.html).
+## Documentation
+
+<div class="two-column" markdown="1">
+
+ - [API
reference](http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html)
+ - [Examples](https://github.com/apache/qpid-jms/tree/0.3.0/qpid-jms-examples)
+ - [Configuration](docs/index.html)
+ - [Building Qpid JMS](building.html)
+
+</div>
+
+## More information
+
+ - [All release artefacts](http://archive.apache.org/dist/qpid/jms/0.3.0)
+ - [Resolved issues in
JIRA](https://issues.apache.org/jira/issues/?jql=project+%3D+QPIDJMS+AND+fixVersion+%3D+%270.3.0%27+ORDER+BY+priority+DESC)
+ - [Source repository
tag](https://git-wip-us.apache.org/repos/asf/qpid-jms.git/tree/refs/tags/0.3.0)
\ No newline at end of file
Added: qpid/site/input/releases/qpid-jms-0.3.0/release-notes.md
URL:
http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-jms-0.3.0/release-notes.md?rev=1685611&view=auto
==============================================================================
--- qpid/site/input/releases/qpid-jms-0.3.0/release-notes.md (added)
+++ qpid/site/input/releases/qpid-jms-0.3.0/release-notes.md Mon Jun 15
16:04:54 2015
@@ -0,0 +1,56 @@
+;;
+;; Licensed to the Apache Software Foundation (ASF) under one
+;; or more contributor license agreements. See the NOTICE file
+;; distributed with this work for additional information
+;; regarding copyright ownership. The ASF licenses this file
+;; to you under the Apache License, Version 2.0 (the
+;; "License"); you may not use this file except in compliance
+;; with the License. You may obtain a copy of the License at
+;;
+;; http://www.apache.org/licenses/LICENSE-2.0
+;;
+;; Unless required by applicable law or agreed to in writing,
+;; software distributed under the License is distributed on an
+;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+;; KIND, either express or implied. See the License for the
+;; specific language governing permissions and limitations
+;; under the License.
+;;
+
+# Qpid JMS 0.3.0 Release Notes
+
+Qpid JMS is a complete [Java Message Service][jms] 1.1 client built
+using the [Qpid Proton](@site-url@/proton/index.html) protocol engine.
+
+For more information about this release, including download links and
+documentation, see the [release overview](index.html).
+
+[jms]: http://en.wikipedia.org/wiki/Java_Message_Service
+
+
+## New features and improvements
+
+ - [QPIDJMS-53](https://issues.apache.org/jira/browse/QPIDJMS-53) - treat
messages with a Data section and common textual content-type values as
TextMessage
+ - [QPIDJMS-55](https://issues.apache.org/jira/browse/QPIDJMS-55) - Add
support for using standard AMQP ports if the URI fails to provide one
+ - [QPIDJMS-61](https://issues.apache.org/jira/browse/QPIDJMS-61) - add
support for setting the sasl / open frame 'hostname'
+ - [QPIDJMS-64](https://issues.apache.org/jira/browse/QPIDJMS-64) - Throw a
JMSException with a more consistent error message when connection attempts fail
+ - [QPIDJMS-70](https://issues.apache.org/jira/browse/QPIDJMS-70) - Add a
redelivery policy to control when the client should reject new deliveries based
on the delivery count.
+
+## Bugs fixed
+
+ - [QPIDJMS-48](https://issues.apache.org/jira/browse/QPIDJMS-48) -
inconsistent handling of property names in Message methods
+ - [QPIDJMS-49](https://issues.apache.org/jira/browse/QPIDJMS-49) - handle
messages with an unknown content-type
+ - [QPIDJMS-52](https://issues.apache.org/jira/browse/QPIDJMS-52) - support
charset parameter in content-type value
+ - [QPIDJMS-54](https://issues.apache.org/jira/browse/QPIDJMS-54) - remove
extraneous indirection around selector verification
+ - [QPIDJMS-56](https://issues.apache.org/jira/browse/QPIDJMS-56) - throw
InvalidClientIDException rather than JMSException when hint present that
container-id was the problem field
+ - [QPIDJMS-57](https://issues.apache.org/jira/browse/QPIDJMS-57) -
ErrorCondition 'info' field lookups should use Symbol keys
+ - [QPIDJMS-58](https://issues.apache.org/jira/browse/QPIDJMS-58) - when a
connection redirect error is received, the original connection details will be
used first
+ - [QPIDJMS-59](https://issues.apache.org/jira/browse/QPIDJMS-59) - uri pool
object is not thread safe but is accessed by multiple threads
+ - [QPIDJMS-60](https://issues.apache.org/jira/browse/QPIDJMS-60) - using
'nested options' causes issues when adding/removing a URI from the pool object
+ - [QPIDJMS-62](https://issues.apache.org/jira/browse/QPIDJMS-62) - ensure
that a body section is always sent when using ObjectMessage
+ - [QPIDJMS-63](https://issues.apache.org/jira/browse/QPIDJMS-63) - SASL
ANONYMOUS doesn't seem to work against the C++ broker
+ - [QPIDJMS-65](https://issues.apache.org/jira/browse/QPIDJMS-65) - updated
SASL mechanism selection to consider available credentials
+ - [QPIDJMS-66](https://issues.apache.org/jira/browse/QPIDJMS-66) - fix
documentation of URI option for ClientID
+ - [QPIDJMS-67](https://issues.apache.org/jira/browse/QPIDJMS-67) - AMQP
header and Open+Close frames are sent after a SASL failure
+ - [QPIDJMS-71](https://issues.apache.org/jira/browse/QPIDJMS-71) - calling
receive(0) on a consumer always returns null
+ - [QPIDJMS-72](https://issues.apache.org/jira/browse/QPIDJMS-72) - update
discovery uri syntax for consistency and add some basic documentation
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
