You probably don't need it, it's for standalone use. With Spring, you just configure the tx manager and the framework should do the rest.
your datasources will need to be XA though.
P.S. well done for reading the docs before posting.
I did assume that would be the case, that Spring should handle it , but I saw a very strange behavior in that :
I found that the transactions do happen but for some reason there is a huge delay in commit, upwards of 15 minutes ! I have no idea why this happens ..any clues ?
That is why I was trying to see if I get to work outside the container ..but facing the below issue..
No idea on the commit delay. Send me a test case, I'll take a look.
Thank you for looking into this.
Im sorry , but Im not sure how I should send a test case. Can I send a deployable archive (ear) .
My app is a jax-ws spring based web service calling 2 different DAO operation s , internally using JDBCTemplate to write to 2 different databases.
A big blob won't do much good. I need source and a way to build it, plus config files etc. Strip your app down to the simplest possible version that reproduces the issue and send me the pieces (src, build script, config files) with documentation of the pre-requisites i.e. versions of java, jboss, spring etc
I removed the webservice layer from the picture , instead the spring pojo service is being invoked from a servlet now. The commit is instantaneous but I am unable to get the rollback working.
The code is something like
throw new RuntimeException();
As I understand , this should rollback the db operations by default. Or do I need to specify explicitly ? Even if I do specify explicitly it only rollbacks the DAO2 db operation. It seems its treating the 2 db operations as 2 different transactions and not 1 as I expect it to be..
Any ideas ?