Standalone Container 1.0 Usage

Uses the apache geronimo transaction and connection manager implementation to provide JCA functionality. Note that this page is intended to be used as a reference. For more information regarding how a container is used within the context of an EOA system, please see the the user guide.

container.xml

The following example defines a Standalone Container definition which must be contained within the file container.xml and located within the 'etc' sub-directory of an alakai system instance. Note that this is an optional step that is only required if you need the functionality of a JCA container, i.e. when your applications and/or other deployed extensions require that alakai provide connection managment, pooling support and/or transaction support.

Examples which demonstrate the configuration of each specific connector type are listed here. For information on each specific configuration setting please refer to comments within the configuration schema. 

<container xmlns="http://bluestemsoftware.org/specification/eoa/ext/container/standalone/1.0/">
  <transactionSupport enable="true">
    <defaultTransactionTimeoutSeconds>800</defaultTransactionTimeoutSeconds>
  </transactionSupport>
  <connectors>
    <connector type="org.bluestemsoftware.specification.eoa.ext.connector.db.DataSourceConnector" impl="org.mycompany1/datasource" name="MyDataSource" >
      <properties>
        <property name="databaseName">fooDB</property>
        <property name="userName">sa</property>
        <property name="password"></property>
      </properties>
      <connectionSupport>
        <transactionSupport type="LOCAL" />
        <poolingSupport type="SINGLE">
          <minPoolSize>1</minPoolSize>
          <maxPoolSize>5</maxPoolSize>
        </poolingSupport>
      </connectionSupport>
    </connector>
  </connectors>
</container>