|
From: Jeppe C. <je...@cr...> - 2006-09-21 21:33:37
|
Hi Thomas As I understand it, SavePoints doesn't directly change the JDBC transaction, you use the JDBC Connection methods to merely issue SQL statements that inform the DB (and it's transaction) that it needs to remember savepoints during it's transaction? But again, it's just a guess based on my assumptions (naive perhaps) on the implementations below. Have anyone tried using SavePoints under JTA? /Jeppe Thomas Risberg wrote: > I'll go the other way - just because the methods are part of the API > doesn't mean that you can use them whenever you want. My guess is that > your JTA implementation will throw an exception if you mess with any > method that manages the JDBC transactions. > > Thomas > > > > Jeppe Cramon wrote: > >> Hi Rod >> >> Thanks for the quick reply. >> >> My interpretation is that since it's standard JDBC it's (of course) supported under JTA. >> But since no one on the team could find anything that stated that it was or wasn't supported, then most unfortunately assumed that it wasn't supported, which is why I went to ask here. >> >> The reason why we're looking at JTA is that we want to be able to use XA when the need arises (which it will because we at a point need to use MQ). >> But since Spring emulated nested transactions aren't available using the JTATransactionManager (or the WebSphere counterpart of it), we were considering writing our own nested trx simulation using SavePoints (since the part where >> we control the nested transactions is well encapsulated). But since no one had tried it before and since most had determined (without facts or at least trying it) that SavePoints doesn't work under JTA we were kind of stuck. >> But you helped us out of it ;-) >> >> Since we now know that SavePoints work under JTA, we should be able to head in the direction, unless of course you have an idea on how we can reuse the existing Spring nested trx. emulation code and still do XA/use MQ transactionally? >> >> Thanks :) >> >> /Jeppe >> >> >> >>> Savepoints are on the JDBC API, aren't they? So they should be >>> supported, *within JTA transaction management*. So you cannot use >>> Spring's nested transaction emulation with a JTA environment. >>> >>> Why do you want to use JTA? >>> >>> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |