...
- Note that
c.dmeanscargo.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 |
| The path to this DataSource in JNDI | Any jndi path, like | mandatory | mandatory | mandatory |
| The implementation class | ex. | mandatory: must implement | mandatory: must implement | mandatory: must implement |
| Properties to pass to the driver | Semi-colon delimited string | optional | optional | mandatory |
| URL for the | ex. | mandatory | mandatory | optional |
| Determines the type of the driver | Defaults to | do not set | do not set |
|
| Determines transaction support type |
| do not set | mandatory | unset defaults to only valid option: |
| Identifier used in configuration files to reference this DataSource | Must contain no path-like characters | optional | optional | optional |
| Username to connect to the database | String | optional | optional | optional |
| Password to connect to the database | String | optional | optional | optional |
JMS resource properties
JMS resources (such as connection factories, queues or topics) are added through pipe-delimited configuration properties that starts with cargo.resource.resource. Example:
...
- Note that
c.rmeanscargo.resource
Property | Purpose | Valid Values | Mandatory? |
|---|---|---|---|
| The ID for the JNDI entry of this JMS resource | ID used in configuration files, if not specified an identifier is created using the name | optional |
| The path to this JMS resource in JNDI | Any JNDI path, like | mandatory |
| Interface of the object | Any JNDI path, like | mandatory |
| Properties to to populate the class with | Semi-colon delimited string; must correspond to setters | optional |
Other resource properties
...
- Note that
c.rmeanscargo.resource
Property | Purpose | Valid Values | Mandatory? |
|---|---|---|---|
| The ID for this JNDI entry | ID used in configuration files, if not specified an identifier is created using the name | optional |
| The path to this resource in JNDI | Any JNDI path, like | mandatory |
| Interface of the object | Any valid interface | mandatory |
| The implementation class | Any valid class implementing the interface | mandatory |
| Properties to to populate the class with | Semi-colon delimited string; must correspond to setters | optional |
Known issues
The Glassfish container has various known issues with regards to DataSource support.
...
ConfigurationFixtureFactory: class with static methods showing examples for creating various DataSource and resource types:createDataSourceandcreateAnotherDataSource: Creation of a DataSourcecreateDriverConfiguredDataSourceWithLocalTransactionSupport: Creation of a DataSource with local transaction supportcreateDriverConfiguredDataSourceWithXaTransactionSupport: Creation of a DataSource with XA transaction supportcreateXADataSourceConfiguredDataSource: Creation of an XA DataSource as DataSourcecreateConnectionPoolDataSourceAsResource: Creation of a connection poolcreateXADataSourceAsResource: Creation of an XA DataSource as a resourcecreateMailSessionAsResource: Creation of a Mail resourcecreateDataSourceWithWindowsPath: Creation of a DataSource with a Windows pathcreateJmsQueueAsResourceandcreateJmsTopicAsResource: Creation of a JMS queue and topic resource, respectively
DataSourceOnStandaloneConfigurationTest: DataSource definition.TransactionEmulationDataSourceOnStandaloneConfigurationTest: DataSource definition with transaction emulation.XATransactionDataSourceOnStandaloneConfigurationTest: XA DataSource definition.MailResourceOnStandaloneConfigurationTest: Resource definition, showing for examplemailsession.JmsResourceOnStandaloneConfigurationTestJmsQueueResourceOnStandaloneConfigurationTestandJmsTopicResourceOnStandaloneConfigurationTest: Resource definition, showing for example a JMS queue and topic, respectively.
Users of the Maven2/Maven3 plugin can use the Maven2 Archetype showing DataSource support. Please read: DataSource Definition Archetype.