ActiveMQ Client Connection Factory

Defining Factory as Dependency

To enable this extension, add its factory as a dependency by pasting the following element into the dependencies section of your alakai system POM. Make sure to populate the version tag with the desired version (check repository for the latest available version).

<dependency>
  <groupId>org.bluestemsoftware.open.eoa.ext.connector.jms.activemq.client</groupId>
  <artifactId>activemq-client-connection-factory</artifactId>
  <version>VERSION</version>
  <scope>runtime</scope>
  <type>eoa-factory</type>
</dependency>

Connector Definition Examples

The example below, defines a JMS connector named 'myConnectionFactory' that can be used to create TCP connections to an activemq server on host 'somehost' listening on port '61616'. Note, to configure an embedded activemq server to accept TCP connections, see the following example. 

<container xmlns="http://bluestemsoftware.org/specification/eoa/ext/container/standalone/1.0/">
  <transactionSupport enable="true" />
  <connectors>
    <connector type="org.bluestemsoftware.specification.eoa.ext.connector.jms.JMSConnector" impl="org.bluestemsoftware.open.eoa.ext.connector.jms.activemq.client.JMSConnectorImpl" name="myConnectionFactory">
      <properties>
        <property name="serverUrl">tcp://somehost:61616</property>
      </properties>
      <connectionSupport>
        <transactionSupport type="LOCAL" />
        <poolingSupport type="SINGLE">
          <minPoolSize>1</minPoolSize>
          <maxPoolSize>10</maxPoolSize>
        </poolingSupport>
      </connectionSupport>
    </connector>
  </connectors>
</container>

Note the example above is defined within the context of a standalone container definition. If you're using a different container implementation, the configuration may look slightly different. See container schema for comments regarding the semantics of the elements used above.