JBoss.org Community Documentation

7.4.1. org.jboss.jms.jndi.JMSProviderLoader MBean

The JMSProviderLoader MBean service creates a JMS provider adaptor and binds it into JNDI. A JMS provider adaptor is a class that implements the org.jboss.jms.jndi.JMSProviderAdapter interface. It is used by the message driven bean container to access a JMS service provider in a provider independent manner. The configurable attributes of the JMSProviderLoader service are:

  • ProviderName : A unique name for the JMS provider. This will be used to bind the JMSProviderAdapter instance into JNDI under java:/<ProviderName> unless overridden by the AdapterJNDIName attribute.

  • ProviderAdapterClass : The fully qualified class name of the org.jboss.jms.jndi.JMSProviderAdapter interface to create an instance of.

  • FactoryRef : The JNDI name under which the provider javax.jms.ConnectionFactory will be bound.

  • QueueFactoryRef : The JNDI name under which the provider javax.jms.QueueConnectionFactory will be bound.

  • TopicFactoryRef : The JNDI name under which the javax.jms.TopicConnectionFactory will be bound.

  • Properties : The JNDI properties of the initial context used to look up the factories.

The RemoteJMSProvider can be referenced on the MDB invoker config as shown in the jboss.xml fragment given in Example 7.14, “ A jboss.xml fragment for specifying the MDB JMS provider adaptor”.

Incidentally, because one can specify multiple invoker-proxy-binding elements, this allows an MDB to listen to the same queue/topic on multiple servers by configuring multiple bindings with different JMSProviderAdapterJNDI settings.

Alternatively, one can integrate the JMS provider using JCA configuration like that shown in Example 7.15, “A jms-ds.xml descriptor for integrating a JMS provider adaptor via JCA”.