Repository: qpid-jms Updated Branches: refs/heads/master 8230546df -> 452c68715
try some alternative indentation Project: http://git-wip-us.apache.org/repos/asf/qpid-jms/repo Commit: http://git-wip-us.apache.org/repos/asf/qpid-jms/commit/452c6871 Tree: http://git-wip-us.apache.org/repos/asf/qpid-jms/tree/452c6871 Diff: http://git-wip-us.apache.org/repos/asf/qpid-jms/diff/452c6871 Branch: refs/heads/master Commit: 452c68715ae9d9cba987f9da14749cc1951d53be Parents: 8230546 Author: Robert Gemmell <[email protected]> Authored: Thu Feb 5 17:31:04 2015 +0000 Committer: Robert Gemmell <[email protected]> Committed: Thu Feb 5 17:31:04 2015 +0000 ---------------------------------------------------------------------- Configuration.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/qpid-jms/blob/452c6871/Configuration.md ---------------------------------------------------------------------- diff --git a/Configuration.md b/Configuration.md index bee8805..4d6de38 100644 --- a/Configuration.md +++ b/Configuration.md @@ -8,11 +8,15 @@ Applications use a JNDI InitialContext, itself obtained from an InitialContextFa 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. + 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 in the next section) 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. + 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, + or in a separate file which is referenced in jndi.properties using the *java.naming.provider.url* property. 2. Via system properties. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
