O'Reilly - Java Message Service

Java Message Service
The constructor of the Chat class starts by obtaining a connection to the JNDI naming
service used by the JMS server:
// Obtain a JNDI connection
Properties env = new Properties( );
// ... specify the JNDI properties specific to the vendor
InitialContext jndi = new InitialContext(env);
Creating a connection to a JNDI naming service requires that a
javax.naming.InitialContext object be created. An InitialContext is the starting point
for any JNDI lookup - it's similar in concept to the root of a filesystem. The
InitialContext provides a network connection to the directory service that acts as a root
for accessing JMS administered objects. The properties used to create an InitialContext
depend on which JMS directory service you are using. The code used to create a JNDI
InitialContext in BEA's Weblogic naming service, for example, would look something
like this:
Properties env = new Properties( );
env.put(Context.SECURITY_PRINCIPAL, "guest");
env.put(Context.SECURITY_CREDENTIALS, "guest");
env.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
InitialContext jndi = new InitialContext(env);
When SonicMQ is used in combination with a third party LDAP directory service, the
connection properties would be very different. For example, the following shows how a
SonicMQ JMS client would use JNDI to access JMS administered objects stored in a
LDAP directory server:
Properties env = new Properties( );
env.put(Context.SECURITY_PRINCIPAL, "guest");
env.put(Context.SECURITY_CREDENTIALS, "guest");
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL,
"ldap://localhost:389/o=acme.com");
InitialContext jndi = new InitialContext(env);
Alternatively, the InitialContext( ) can be created without
properties (no-arg constructor). In this case JNDI will read the
vendor-specific JNDI properties from a special file in the classpath
named jndi.properties. This eliminates provider-specific code in JMS
clients, making them more portable.
23