I would like to have your opinion…
I should like to use Spring interceptor mechanism for transaction on files CRUD operation.

Please look at this post: http://forum.springframework.org/showthread.php?p=161920#post161920

Thanks a lot for your help.

Cheers,
Stephane

So JOTM isn’t any good, then?

Cheers,
Tracey

Thanks again…

================================================================
Cool info! But I have Tomcat 5.5 and Spring 1.2.8, and two completely different databases, (iSeries via IBatis and JTOpen, PC SQL MySql & MSSQL Server & Postgresql) and I need to implement service-level transaction control over both of them.

Everything I see tells me that I need JOTM to allow Spring to do that using JTA, as Tomcat doesn’t natively support it… is there a better way?

I’m having zero luck in even setting it up via Spring, so any help gratefully recieved.

Cheers
Tracey

Reliability through atomicity, the easiest way: this product is a premium transaction manager for automatic cancelation of problematic transactions, across disparate datasources or back-end systems. Unlike CICS™ (IBM, mainframe) or Tuxedo™ (Bea, workstations), our product is optimized for easy integration into Java™-based solutions:

open source: gives you control and transparency (apache license)
professional support available directly from the developers
very easy to learn in less than 1 day (includes demos and docs)
a very small memory footprint
100% Java™: seamless compatibility with any Java™ application
JTA/XA compliant: instant JTA/XA transactions with full recovery and nested transactions
Integration into your code can be as simple as one line of code… Because it’s open source, this product is completely yours to use

Thank you for this blog. I have been battling with myself whether or not to replace an exising part of a system I maintain that currently polls a database table ( by continually SELECTing from the table ) for new “messages” … and replace it with JMS message queue which is more natural.

Problem then is, I need to have JMS operations + other JDBC operations as part of a single transaction, even if I will be persisting JMS to the same database that the other JDBC operations will operate against.

Of course with JMS, the actual persistence is abstracted and therefore, you don’t get access to the JDBC connection ( the JMS provider could be persisting to a file ). Thus, the only way it would work was if both JMS and JDBC were XA resources. However, going back to the scenario that I have …. there is really just one database for both JMS and JDBC ops.

Since I only have one database, does my RDBMS ( Sybase ASE ) therefore need to be XA-enabled ? Do I still need XA-enabled JDBC drivers ?

My personal answers are yes and yes, since you will essentially have 2 connections to the same database, and the transactions on both connections will still need to participate in 2PC.

Furthermore, I could not find a decent open-source stand-alone JTA provider that does XA recovery ( JOTM probably now does, who knows ).