Contains some default SHIM's to interface with JNDI - so that clients can use our JMS provider without ANY code level ties.
The ideal way to use JNDI is to have administrator configure JNDI such that a well-known jndi NAME is bound to "org.apache.hedwig.jms.spi.HedwigConnectionFactoryImpl" for Topic and JMS connection factory.

Alternatively, if the user is NOT within an admin controlled JNDI environment, there are two other common options :

In either of these two cases, we expose 6 well defined 'names' for users, to pull the relevant factories from the JNDI context.
JNDI name Connection factory
jms/ConnectionFactory ConnectionFactory
jms/TopicConnectionFactory TopicConnectionFactory
jms/QueueConnectionFactory QueueConnectionFactory
ConnectionFactory ConnectionFactory
TopicConnectionFactory TopicConnectionFactory
QueueConnectionFactory QueueConnectionFactory