Hi there, We are using OJB (0.9.7) for implementing a project on a Websphere App Server (WAS), v.4.0. Access to the OJB layer is strictly from session EJB's (or helper classes). The database is Oracle 9i.
OJB works great for retrieving data and everyone is very happy about it. However, I'm a bit confused with regards to transactions when using the ODMG API for creating / modifying persistent objects. (We consider using OJB instead of entity beans, not for implementing BMP entity beans). My OJB.properties file currently looks like this: #---------------------------------------------------------------------------------------- # Transaction Management and assocation #---------------------------------------------------------------------------------------- # Use the LocalTxManager if you want the transaction to be associated by a thread # OJBTxManagerClass=org.apache.ojb.odmg.LocalTxManager # Use the JTATxManager if you want the transaction to be associated via the Transaction # manager that is in your application server. OJBTxManagerClass=org.apache.ojb.odmg.JTATxManager # # WebSphere transaction manager factory JTATransactionManagerClass=org.apache.ojb.otm.transaction.factory.WebSphereTransactionManagerFactory ... However using this configuration beginning a transaction will fail. (The same code runs fine using the LocalTxManager). Running the debugger in WSAppDeveloper v5 I found out that the WebSphereTransactionManagerFactory will try to access a class named com.ibm.ejs.jts.jta.JTSXA (actually in the original OJB source mispelled as com.ibm.ejcs.jts.jta.JTSXA) to get a TransactionManager. This seems to do go well, I don't get any ClassNotFound or other exceptions. However the returned TransactionManager will not return a transaction when asked for it. So, has anyone ever got this working? Or should I use another approach? For instance, can it harm to use the LocalTxManager in an app server architecture like the one I described? Any help deeply appreciated. Best regards, have a good X-mas time, Jeroen Pielage Antares the Netherlands -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
