Repository: qpid-jms
Updated Branches:
  refs/heads/master 452c68715 -> b576d7923


more formatting tweaks


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

Branch: refs/heads/master
Commit: b576d7923c246ec881f6c95dd09b07d29fbcd506
Parents: 452c687
Author: Robert Gemmell <[email protected]>
Authored: Thu Feb 5 17:34:27 2015 +0000
Committer: Robert Gemmell <[email protected]>
Committed: Thu Feb 5 17:34:27 2015 +0000

----------------------------------------------------------------------
 Configuration.md | 27 +++++++++++++++++++--------
 1 file changed, 19 insertions(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/qpid-jms/blob/b576d792/Configuration.md
----------------------------------------------------------------------
diff --git a/Configuration.md b/Configuration.md
index 4d6de38..7e07fb6 100644
--- a/Configuration.md
+++ b/Configuration.md
@@ -12,7 +12,7 @@ Applications use a JNDI InitialContext, itself obtained from 
an InitialContextFa
   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();
+      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,
@@ -20,30 +20,41 @@ Applications use a JNDI InitialContext, itself obtained 
from an InitialContextFa
 
 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.
+  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();
+      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 in the next section.
+  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.
 
 3. Programatically using an environment Hashtable.
 
-    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);
+      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 in 
the next section), 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 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
+  separate file which is referenced using the *java.naming.provider.url* 
property within the environment Hashtable.
 
 ## Qpid JmsInitialContextFactory properties syntax
 
 * To define a ConnectionFactory: connectionfactory.lookupName = URI
+
     connectionfactory.myFactoryLookup = amqp://localhost:5672
+
 * To define a Queue: queue.lookupName = queueName
+
     queue.myQueueLookup = queueA
+
 * To define a Topic: topic.lookupName = topicName
+
     topic.myTopicLookup = topicA
 
 These objects could then be looked up from a Context as follows:
+
     ConnectionFactory factory = (ConnectionFactory) 
context.lookup("myFactoryLookup");
     Destination queue = (Destination) context.lookup("myQueueLookup");
     Destination topic = (Destination) context.lookup("myTopicLookup");


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

Reply via email to