Ey Up,
Tring to configure an xa datasource for Progress 9.1D (thats NOT pgsql) unfortunatly it does not support transactions via jdbc.
I have a non-xa datasource and would like to add another using a wrapper but can't find an example for 3.0.x. Managed to have something working months ago on JBoss 2.4 with the old style.
Help would be apreciated.
Ta, Tim.
Current non-xa datasource....
<?xml version="1.0" encoding="UTF-8"?>
<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->
ProgressDS
<config-property name="ConnectionURL" type="java.lang.String">jdbc\:jdbcprogress\:T\:128.1.1.6\:4093\:hr</config-property>
<config-property name="DriverClass" type="java.lang.String">com.progress.sql.jdbc.JdbcProgressDriver</config-property>
<!--set these only if you want only default logins, not through JAAS -->
<config-property name="UserName" type="java.lang.String">Me</config-property>
<config-property name="Password" type="java.lang.String">apasswd</config-property>
<!--Below here are advanced properties -->
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->
0
50
5000
15
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
ByContainer
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager
java:/TransactionManager
<!--make the rar deploy! hack till better deployment-->
jboss.jca:service=RARDeployer