Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Container support

Here are the configurations that currently support DataSource or Resource configuration:

Container

Configuration

Resource

DataSource

Transactional DataSource

XA DataSource

GlassFish 3.x

o.c.c.c.glassfish.GlassFish3xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

JOnAS 4.x

o.c.c.c.jonas.Jonas4xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

JOnAS 5.x

o.c.c.c.jonas.Jonas5xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

Oc4J 9.x

o.c.c.c.orion.Oc4j9xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

Oc4J 10.x

o.c.c.c.orion.Oc4j10xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

Resin 2.x

o.c.c.c.resin.Resin2xStandaloneLocalConfiguration

(tick)

(tick)

(error)

(tick)

Resin 3.x

o.c.c.c.resin.Resin3xStandaloneLocalConfiguration

(tick)

(tick)

(error)

(tick)

Tomcat 4.x

o.c.c.c.tomcat.Tomcat4xStandaloneLocalConfiguration

(tick)

(tick)

(error)

(error)

Tomcat 5.x

o.c.c.c.tomcat.Tomcat5xStandaloneLocalConfiguration

(tick)

(tick)

(error)

(error)

Tomcat 6.x

o.c.c.c.tomcat.Tomcat6xStandaloneLocalConfiguration

(tick)

(tick)

(error)

(error)

Tomcat 7.x

o.c.c.c.tomcat.Tomcat7xStandaloneLocalConfiguration

(tick)

(tick)

(error)

(error)

WebLogic 8.x

o.c.c.c.weblogic.WebLogicStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

WebLogic 9.x

o.c.c.c.weblogic.WebLogic9xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

WebLogic 10.x

o.c.c.c.weblogic.WebLogic10xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

WebLogic 10.3.x

o.c.c.c.weblogic.WebLogic10xStandaloneLocalConfiguration

(error)

(tick)

(tick)

(tick)

Notes:

DataSource properties

DataSources are added through pipe-delimited configuration properties that starts with cargo.datasource.datasource. Example:

Here are the properties that are valid for this:

  • Note that c.d means cargo.datasource
  • Note that if you specify a property marked do not set you will get a CargoException.

Property

Purpose

Valid Values

DataSource

Transactional DataSource

XA DataSource

c.d.jndi

the path to this in jndi

any jndi path, like jdbc/userds

mandatory

mandatory

mandatory

c.d.driver

the implementation class

ex. my.Driver

mandatory: must implement java.sql.Driver

mandatory: must implement java.sql.Driver

mandatory: must implement javax.sql.XADataSource

c.d.properties

properties to pass to the driver

semi-colon delimited string

optional

optional

mandatory

c.d.url

url for the java.sql.Driver

ex. jdbc:host:port/mydb

mandatory

mandatory

optional

c.d.type

Determines the type of the driver

defaults to java.sql.Driver, only set if you want to use a javax.sql.XADataSource

do not set

do not set

javax.sql.XADataSource

c.d.transactionsupport

what transaction support

LOCAL_TRANSACTION or XA_TRANSACTION

do not set

mandatory

unset defaults to only valid option: XA_TRANSACTION

c.d.id

used in configuration files to reference this datasource

must contain no path-like characters

optional

optional

optional

c.d.username

username to connect to the db

string

optional

optional

optional

c.d.password

password for the username

string

optional

optional

optional

Resource properties

Resources are added through pipe-delimited configuration properties that starts with cargo.resource.resource. Example:

Here are the properties that are valid for this:

  • Note that c.r means cargo.resource

Property

Purpose

Valid Values

Mandatory?

c.r.name

the path to this in jndi

any jndi path, like resource/apple

mandatory

c.r.type

Interface of the object

valid interface

mandatory

c.r.class

the implementation class

valid class implementing the interface

mandatory

c.r.parameters

properties to to populate the class with

semi-colon delimited string; must correspond to setters

optional

Examples

Users of the Java API can take a look at the following classes as example:

  • DataSourceOnStandaloneConfigurationTest: datasource definition.
  • TransactionEmulationDataSourceOnStandaloneConfigurationTest: datasource definition with transaction emulation.
  • XATransactionDataSourceOnStandaloneConfigurationTest: XA datasource definition.
  • ResourceOnStandaloneConfigurationTest: resource definition, showing for example mailsession.

Users of the Maven2/Maven3 plugin can use the Maven2 Archetype showing datasource support. Please read: Datasource Definition Archetype.

  • No labels