Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B89F4200C12 for ; Wed, 28 Dec 2016 11:37:27 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B70D9160B45; Wed, 28 Dec 2016 10:37:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6C441160B5A for ; Wed, 28 Dec 2016 11:37:23 +0100 (CET) Received: (qmail 73484 invoked by uid 500); 28 Dec 2016 10:37:22 -0000 Mailing-List: contact commits-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@qpid.apache.org Delivered-To: mailing list commits@qpid.apache.org Received: (qmail 72837 invoked by uid 99); 28 Dec 2016 10:37:22 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2016 10:37:22 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id D0667F2DC9; Wed, 28 Dec 2016 10:37:21 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: orudyy@apache.org To: commits@qpid.apache.org Date: Wed, 28 Dec 2016 10:37:45 -0000 Message-Id: <4017494d1c4843f3a07dd9bdd6bd47f6@git.apache.org> In-Reply-To: <9a668f1bb56f4133b558ca5211b30157@git.apache.org> References: <9a668f1bb56f4133b558ca5211b30157@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [25/51] [partial] qpid-site git commit: Update site for 6.1.1 release of Qpid Java archived-at: Wed, 28 Dec 2016 10:37:28 -0000 http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies-Dependencies.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies-Dependencies.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies-Dependencies.html new file mode 100644 index 0000000..d7ca18c --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies-Dependencies.html @@ -0,0 +1,146 @@ + + + + + 3.2. Dependencies - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
3.2. Dependencies
Prev Chapter 3. Getting the Client And Dependencies Next

3.2. Dependencies

The Client has minimal set of external dependencies.

It requires:

  • JDK 1.7 or higher.

  • JMS 1.1 specification (such as geronimo -jms_1.1_spec JAR)

  • Apache SLF4J (slf4j-api-x.y.z JAR)

+

The use of SLF4J means that application authors are free to plug in any logging framework + for which an SLF4J binding exists.

Prev Up Next
Chapter 3. Getting the Client And Dependencies Home Chapter 4. Examples
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies.html new file mode 100644 index 0000000..e0c929a --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies.html @@ -0,0 +1,154 @@ + + + + + Chapter 3. Getting the Client And Dependencies - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
Chapter 3. Getting the Client And Dependencies
Prev   Next

Chapter 3. Getting the Client And Dependencies

Table of Contents

3.1. Getting the Client
3.2. Dependencies

3.1. Getting the Client

The Apache Qpid JMS client for AMQP 0-9-1/0-10 is available as a bundle or from Maven repositories.

The bundle (a .tar.gz) includes the Client itself (formed by two JAR: qpid-client + and qpid-common) together with slf4j-api, and geronimo-jms_1.1_spec. There is also a qpid-all + JAR artifact that, for convenience, includes a manifest classpath that references the other + JARs. The bundle is available from the Apache Qpid project web site.

The Client is also available from Maven repositories. Add the following + dependency:

+    <dependency>
+      <groupId>org.apache.qpid</groupId>
+      <artifactId>qpid-client</artifactId>
+      <version>6.1.1</version>
+    </dependency>
+

Appendix B, Minimal Maven POM illustrates a minimal Maven POM required to use the Qpid Client.

Prev   Next
Chapter 2. Document Scope And Intended Audience Home 3.2. Dependencies
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Destination.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Destination.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Destination.html new file mode 100644 index 0000000..a276859 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Destination.html @@ -0,0 +1,146 @@ + + + + + 6.4. Destination - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
6.4. Destination
Prev Chapter 6. JNDI Properties Format Next

6.4. Destination

destination.name declares either a Queue or Topic (depending on the class) with the + given JNDI name. The value must be a Binding URL.

See Chapter 8, Binding URL for format of the URL and its permitted + options.

Prev Up Next
6.3. Topic Home Chapter 7. Connection URLs
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Queue.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Queue.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Queue.html new file mode 100644 index 0000000..ebe047b --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Queue.html @@ -0,0 +1,145 @@ + + + + + 6.2. Queue - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
6.2. Queue
Prev Chapter 6. JNDI Properties Format Next

6.2. Queue

queue.name declares a Queue with the given JNDI name. The + value is simple queue name. This is the name of the queue as known by the Broker.

The queue. form is a short hand for declaring a destination:

destination.name=direct://amq.direct//<queue name>?routingkey=’<queue name>’&durable=’true’
Prev Up Next
Chapter 6. JNDI Properties Format Home 6.3. Topic
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Topic.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Topic.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Topic.html new file mode 100644 index 0000000..c7c81ac --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Topic.html @@ -0,0 +1,147 @@ + + + + + 6.3. Topic - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
6.3. Topic
Prev Chapter 6. JNDI Properties Format Next

6.3. Topic

topic.name declares a Topic with the given JNDI name. The + value is topic name. This topic name is used on the Broker as a binding key between the + amq.topic exchange and the queue corresponding to the topic + subscriber.

The topic. form is a short hand for declaring a destination:

destination.name=topic://amq.topic/<topic name>/?routingkey=<topic name>
Prev Up Next
6.2. Queue Home 6.4. Destination
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format.html new file mode 100644 index 0000000..46407e7 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format.html @@ -0,0 +1,157 @@ + + + + + Chapter 6. JNDI Properties Format - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
Chapter 6. JNDI Properties Format
Prev   Next

Chapter 6. JNDI Properties Format

Table of Contents

6.1. ConnectionFactory
6.2. Queue
6.3. Topic
6.4. Destination

The Client comes with own JNDI context factory + org.apache.qpid.jndi.PropertiesFileInitialContextFactory which utilises a + Java properties file for declaring the JMS administered objects: connection factories, queues, + topics and destinations. It uses the following syntax:

+ 

+connectionfactory.<jndi name>=<connection url>
+queue.<jndi name>=<queue name>
+topic.<jndi name>=<topic name>
+destination.<jndi name>=<binding url>
+

An arbitrary number of connection factories, queues, topics, queues or destinations or can + be declared in the JNDI properties file. Each JNDI name must be unique.

The application looks up the objects via an InitialContext. This lookup and an example JNDI + properties file is provided in Chapter 4, Examples

We now consider each JMS administered object type in turn.

6.1. ConnectionFactory

connectionfactory.name declares a ConnectionFactory with the + given JNDI name. The value must be a legal Connection URL.

See Chapter 7, Connection URLs for format of the URL and its + permitted options.

Prev   Next
5.7. Destinations Home 6.2. Queue
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging-EnablingDebugLogging.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging-EnablingDebugLogging.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging-EnablingDebugLogging.html new file mode 100644 index 0000000..e0cf086 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging-EnablingDebugLogging.html @@ -0,0 +1,151 @@ + + + + + 11.2. Enabling Debug - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
11.2. Enabling Debug
Prev Chapter 11. Logging Next

11.2. Enabling Debug

If you are experiencing a problem, it can be informative to enable debug logging to allow + the behaviour of the Client to be understood at a deeper level.

To do this, set the org.apache.qpid logger to + DEBUG.

If you are using Apache Log4j with a log4j.properties file, this simply means adding (or + changing) the following line:

+      log4j.logger.org.apache.qpid=DEBUG
+

If you are using another logging framework, or you are using Log4j but configuring in + another manner, refer to the documentation accompanying the logging framework for details of + how to proceed.

Prev Up Next
Chapter 11. Logging Home Appendix A. Exceptions
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

+
+
+
+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging.html b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging.html new file mode 100644 index 0000000..b8f1ce1 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/jms-client-0-8/book/JMS-Client-0-8-Logging.html @@ -0,0 +1,155 @@ + + + + + Chapter 11. Logging - Apache Qpid™ + + + + + + + + + + + + + +
+
+ Menu + + Search + + +
+ + + + + +
+ + +
+
Chapter 11. Logging
Prev   Next

Chapter 11. Logging

Table of Contents

11.1. Recommended Production Logging Level
11.2. Enabling Debug< /a>

The Client uses the Apache SLF4J logging + framework. All logging activity created by the client is directed through the SLF4J API. SLF4J + is a is a façade for other common logging frameworks. This makes it easy for application authors + to use their prefered logging framework in their application stack, and have the Client + use it too.

SLF4J suppplies bindings for many common logging frameworks (JUL, Apache Log4J, Logback.

Include the SLF4J binding corresponding to the logging framework of your choosen logging + framework on classpath. For full details, see the SLF4J documentation.

11.1. Recommended Production Logging Level

In production, it is recommended that you configure your logging framework is configured + with logger org.apache.qpid set to WARN.

If you are using Apache Log4j with a log4j.properties file, this simply means adding the + following line:

+      org.apache.qpid=WARN
+

If you are using another logging framework, or you are using Log4j but configuring in + another manner, refer to the documentation accompanying the logging framework for details of + how to proceed.

Prev   Next
Chapter 10. System Properties Home 11.2. Enabling Debug
+ +
+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; 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 +

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