Re: [Springframework-developer] TransactionSynchronization invoked even when participating in existing transaction

[Andy D. <an...@ma...>]

Wow, this is great response time!  This has become quite an issue for us, and 
it looks like this should solve the issue nicely.

Thanks,
  Andy

On Friday 24 June 2005 08:26 am, Juergen Hoeller wrote:
> Indeed, in case of an existing JTA transaction, we should try to register
> with the JTA TransactionManager and at least synchronize the
> "afterCompletion" callback (which receives a transaction status - committed
> or rolled back) with the outer transaction.
>
> I've just reworked AbstractPlatformTransactionManager and
> JtaTransactionManager accordingly, registering a corresponding JTA
> Synchronization if the JTA TransactionManager is available. Else, it will
> still call "afterCompletion" immediately at completion of the Spring
> transaction demarcation, but pass in "STATUS_UNKNOWN" now, as we
> effectively don't know whether the outer JTA transaction is gonna commit or
> roll back.
>
> This will be shipped in Spring 1.2.2, to be released tonight.
>
> Juergen