Atomikos Forum |
|
I was wondering if JTA.properties is mandatory to wotk with Atomikos.
In our App, we have basically three strategies: Hibernate transaction manager (no JTA), atomikos, and the transaction manager of the application container, when applicable. The tree strategies are defined in three separate Spring config files. At runtime, we simply choose the strategy we want to use by importing one of those three files. Is there a typical sample of jta.properties that we should use? Any side effect if the transaction manager of the container is used instead?
Hi,
You can use the Spring config to replace the jta.properties, as explained here: http://www.atomikos.com/Documentation/SpringIntegration#The_Advanced_Case_As_of_3_3 HTH Guy
Hey Guy,
I have upgraded to this config but I still have this when I start the spring container No properties path set - looking for transactions.properties in classpath... transactions.properties not found - looking for jta.properties in classpath... Failed to open transactions properties file - using default values |