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);
On 11/04/2008, Vannel <[EMAIL PROTECTED]> wrote:
>
> Sorry about not being clear. Initially I was trying to give an example and in
> the later post I decided to give a more accurate representation of my
> program. I dont think I am using any form of caching unless it's on by
> default. To be ab
Hi Vannel,
As I understand it, iBATIS will issue each of your SQL statements
(select, update) to the database in turn. However, the "return" (I
assume you mean the result of the update() call) will only happen once
both statements have been executed.
I'm still a bit confused as to what your appl
are externally managed transactions, the iBATIS rollback will
> mark the external transaction for rollback, but the other two methods do,
> essentially, nothing.
>
> Jeff Butler
>
>
> On Tue, Apr 8, 2008 at 9:44 AM, Alistair Young <[EMAIL PROTECTED]>
> wrote:
>
&g
3. The iBATIS rollback marks the transaction for rollback, but does not
> rollback itself
> >
> > When there are externally managed transactions, the iBATIS rollback will
> mark the external transaction for rollback, but the other two methods do,
> essentially, nothing.
> >
On 09/04/2008, Vannel <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a performance issue i'm not sure how to solve effectively. Here's my
> situation..
> I'm trying to run INSERT/UPDATE/DELETE statements and using their return
> values as confirmation that the statement has been duly completed
Once again I seem to have found a solution shortly after asking the question...
On 08/04/2008, Alistair Young <[EMAIL PROTECTED]> wrote:
> [ ... snip ... ]
>
>// start a transaction
>// [iBATIS starts a new JTA transaction...?]
>sqlMapCl
Hello again,
After figuring out my previous problem, I've got my iBATIS/JTA test
application working up to a point (start transaction, update followed
by end or commit).
Now, according to the book "iBATIS in Action", when configured to use
a JTA transactionManager, "iBATIS will look for the globa
On 08/04/2008, Alistair Young <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I've been using iBATIS for a while quite successfully with a
> transactionManager type of "JDBC" - however, I now want to use JTA and
> am not having so much luck.
>
> [ ... s
Hello all,
I've been using iBATIS for a while quite successfully with a
transactionManager type of "JDBC" - however, I now want to use JTA and
am not having so much luck.
I have a block of code like this:
// start a transaction
dao.startTransaction();
// get and update a
10 matches
Mail list logo
