I have a question about nesting iBATIS transactions. Or, at least,
being able to write methods which will work in an iBATIS transactional
context whether or not one has been imposed externally.
Consider the following bit of sample code:
sqlMap.startTransaction();
sqlMap.update(XXX, xxx);
Is there a better way of dealing with this?
I go for Spring framework's declarative transactions. Spring has support for
iBatis and definitely it'll save your headache.
Sorry, 'it'll save your headache' should read 'it'll save you from your
headache' ;)
On Thu, Apr 17, 2008 at 1:06 AM, Koka Kiknadze [EMAIL PROTECTED] wrote:
Is there a better way of dealing with this?
I go for Spring framework's declarative transactions. Spring has support for
iBatis and
