qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rob...@apache.org
Subject qpid-jms git commit: consolidate the jndi property syntax definition into the previous section
Date Fri, 06 Feb 2015 12:39:09 GMT
Repository: qpid-jms
Updated Branches:
  refs/heads/master 280be6eea -> 990de5a2b


consolidate the jndi property syntax definition into the previous section


Project: http://git-wip-us.apache.org/repos/asf/qpid-jms/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-jms/commit/990de5a2
Tree: http://git-wip-us.apache.org/repos/asf/qpid-jms/tree/990de5a2
Diff: http://git-wip-us.apache.org/repos/asf/qpid-jms/diff/990de5a2

Branch: refs/heads/master
Commit: 990de5a2bdbaca9b0d60a254b86ef7f5c9b8e60a
Parents: 280be6e
Author: Robert Gemmell <robbie@apache.org>
Authored: Fri Feb 6 12:39:00 2015 +0000
Committer: Robert Gemmell <robbie@apache.org>
Committed: Fri Feb 6 12:39:00 2015 +0000

----------------------------------------------------------------------
 qpid-jms-docs/Configuration.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/qpid-jms/blob/990de5a2/qpid-jms-docs/Configuration.md
----------------------------------------------------------------------
diff --git a/qpid-jms-docs/Configuration.md b/qpid-jms-docs/Configuration.md
index b20b5e3..e062a45 100644
--- a/qpid-jms-docs/Configuration.md
+++ b/qpid-jms-docs/Configuration.md
@@ -15,7 +15,7 @@ Applications use a JNDI InitialContext, itself obtained from an InitialContextFa
         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 in the next section) either directly within
the jndi.properties file,
+    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.
@@ -27,7 +27,7 @@ Applications use a JNDI InitialContext, itself obtained from an InitialContextFa
 
     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
-    in the next section.
+    below.
 
 3.  Programatically using an environment Hashtable.
 
@@ -38,18 +38,18 @@ Applications use a JNDI InitialContext, itself obtained from an InitialContextFa
         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 in the next section), either directly within the environment
Hashtable, or in a
+    (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.
 
-### Qpid JmsInitialContextFactory properties syntax
-
 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 example, consider the following properties to define a ConnectionFactory, Queue, and
Topic:
+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


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


Mime
View raw message