User: mulder
Date: 00/10/20 22:20:21
Modified: src/etc/conf jboss.properties
Log:
Make jBoss work with Oracle XADataSource driver.
Not yet a very elegant solution - we need to be able to use a different
Xid implementation class per pool for this to really work right.
The requirements of the Oracle driver were:
- Xid must be instanceof OracleXid
- Global and Branch IDs must be exactly 64 bytes
- RM that end is called on must be *exactly* the same as start
was called on (XAConnection.getXAResource returns a different
instance each time *despite* the documented 1-to-1 relation)
- Can't execute DDL (create/drop table, etc) within a transaction
Haven't tested this well with multiple data sources - that's next.
Revision Changes Path
1.5 +2 -1 jboss/src/etc/conf/jboss.properties
Index: jboss.properties
===================================================================
RCS file: /products/cvs/ejboss/jboss/src/etc/conf/jboss.properties,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- jboss.properties 2000/10/09 20:18:45 1.4
+++ jboss.properties 2000/10/21 05:20:21 1.5
@@ -3,7 +3,8 @@
#java.rmi.server.useLocalHostName=true
#java.rmi.server.hostname=localhost
#java.rmi.server.codebase=http://localhost:8080/
-
+#jboss.xa.xidclass=oracle.jdbc.xa.OracleXid
+
jdbc.drivers=org.hsql.jdbcDriver,jdbc.idbDriver
#java.security.manager=java.lang.SecurityManager
