SAP-DB doesn't have native XA transaction support; the JDBC driver sort of fakes it, but won't have exactly correct semantics. See the wiki (sapdb.2scale.net) for more details. I don't know if CMP would actually work properly between weblogic and sap-db.
You might be better off making a lightweight persistence layer of your own. Make a simple entity-only O-R mapping framework (i.e. don't try to automate populating relationships, which is surprisingly hard to implement). This will give you most of the useful feature set of a bean container - reflective population, optimistic off-line concurrency and automating most of the grunt work of SQL generation). This level of functionality isn't hard to implement, maybe 2K LOC in java, half that in Python. Nigel. -----Original Message----- From: Norbert Mende [mailto:[EMAIL PROTECTED] Sent: Thursday, 7 August 2003 4:38 a.m. To: [EMAIL PROTECTED] Subject: EJBs with CMP, KeepXAConnTillTxComplete, TRANSACTION_SERIALIZABLE Hi, I'm working on EJBs with container managed persistence with BEA WebLogic. When trying BEA's primary key generator, a java.sql.SQLException occurs: Cannot set transaction isolation level for the XA connection if the XA connection pool does not have "KeepXAConnTillTxComplete" attribute set to true. The BEA-manual tells something about isolation-level TRANSACTION_SERIALIZABLE and that it is needed for the key generator. Does SAP DB support this isolation-level? My test-EJB is connected to the database by using a jdbc-datasource with a connection-pool and com.sap.dbtech.jdbcext.XADataSourceSapDB. All other operations are working fine so far. Any ideas or explanations on this topic are appreciated. Regards, Norbert Mende _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
