...
The created DataSource will also be given the osgi.jndi.service.name property. So if aries jndi is present it will automatically be available using jndi. So it can be used in a persistence.xml.
Properties
| Key | Description |
|---|---|
| osgi.jdbc.driver.name | Identify the DataSourceFactory by name |
| osgi.jdbc.driver.class | Identify the DataSourceFactory by class |
| dataSourceName | Will be set as dataSourceName as well as osgi.jndi.service.name in the published service |
| * | All other local properties (not containing a dot) are forwarded to the DataSourceFactory to create the DataSource. Additionally, properties prefixed with "jdbc." will also be forwarded, the prefix being discarded. For instance "username" will be forwarded, but "aries.xa.name" will not be forwarded to the DataSourceFactory (but published as service properties in the service registry). |
Properties are also published as service properties in the service registry. Hidden properties are supported (starting with a dot, e. g. ".password"). Such properties are not shown in the service registry, however, they are forwared to the DataSourceFactory (without the leading dot).
Installation in karaf 3
Create config in etc/org.ops4j.datasource-test.cfg:
...