[EMAIL PROTECTED] wrote:
If you are using Spring then you should be leverage the power of
letting Spring manage the transactions for you with an interceptor.
This is relatively painless to configure and you do not have to do
anything in your code pertaining to transactions. Look in the examples
directory of Spring and pay attention to the petstore sample app for
configuring your transitions. This app is using iBatis for the
persistence layer and has good examples for both local transactions as
well as distributed transactions.
Thanks. I'm actually quite familiar with Spring's handy transaction
stuff - I've done a number of webapps using Spring with Hibernate which
take advantage of the feature. In this particular rather specialised
instance, though, I want to do transactions 'the Ibatis way', just using
the Spring classes.
John
--
==============================================
John Moore - Norwich, UK - [EMAIL PROTECTED]
==============================================