Examples of org.activemq.ActiveMQXAConnectionFactory

org.activemq.ActiveMQXAConnectionFactory

The XAConnectionFactory interface is a base interface for the XAQueueConnectionFactory and XATopicConnectionFactory interfaces.

Some application servers provide support for grouping JTS capable resource use into a distributed transaction (optional). To include JMS API transactions in a JTS transaction, an application server requires a JTS aware JMS provider. A JMS provider exposes its JTS support using an XAConnectionFactory object, which an application server uses to create XAConnection objects.

XAConnectionFactory objects are JMS administered objects, just like ConnectionFactory objects. It is expected that application servers will find them using the Java Naming and Directory Interface (JNDI) API.

The XAConnectionFactory interface is optional. JMS providers are not required to support this interface. This interface is for use by JMS providers to support transactional environments. Client programs are strongly encouraged to use the transactional support available in their environment, rather than use these XA interfaces directly. @version $Revision: 1.1.1.1 $ @see javax.jms.ConnectionFactory

      System.out.println("ActiveMQ provider starting up.");
      System.out.println("==================================");
      
      directory.put(getQueueConnectionFactory(), new ActiveMQConnectionFactory(brokerURL));
        directory.put(getTopicConnectionFactory(), new ActiveMQConnectionFactory(brokerURL));
        directory.put(getXAQueueConnectionFactory(), new ActiveMQXAConnectionFactory(brokerURL));
        directory.put(getXATopicConnectionFactory(), new ActiveMQXAConnectionFactory(brokerURL));


    if( adminConnection!=null )
      throw new JMSException("Admin connection allready established.");
    
        ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory(brokerURL);

Examples of org.activemq.ActiveMQXAConnectionFactory

Related Classes of org.activemq.ActiveMQXAConnectionFactory