[hibernate-dev] discussion about impact of using TransactionSynchronizationRegistry in AS7...

[Scott Marlow]

Yes, I meant Hibernate subprojects.  Thanks for the answer.

On 06/01/2011 04:45 PM, Steve Ebersole wrote:
> If you mean Hibernate subprojects, they should all be registering synchs
> through Hibernate which then delegates transaction events to them.  This was
> specifically discussed to circumvent problems we had with multiple
> registrations and callbacks happening "out of order" with certain JTA
> implementations.
> On Jun 1, 2011 2:56 PM, "Scott Marlow"<smarlow at redhat.com>  wrote:
>> I posted a message on the as7-dev ml
>> (http://lists.jboss.org/pipermail/jboss-as7-dev/2011-May/002254.html),
>> about switching to use the TransactionSynchronizationRegistry.
>>
>> Do any Hibernate projects currently register Transaction synchronization
>> objects? Do they currently register synchronizations via
>> TransactionSynchronizationRegistry (TSR)? I already know the answer for
>> Hibernate 4.0 core (integration code can influence either interface to
>> be used (TX or TSR)).
>>
>> I'm trying to get a sense for, what would happen if container managed
>> (AS7) session beans were registered with the active JTA transaction via
>> the TSR.
>>
>> If AS7 switches to use the TSR, I think that Hibernate might need to
>> ensure that it doesn't attempt to register with the TX too late.
>>
>> See http://pastie.org/1836698 for an example of what would happen if a
>> TSR synchronization object is already present and someone tries to
>> register a TX synchronization after tx.commit has been started.
>>
>> I cross posted a similar message on Infinispan-dev for input...
>>
>> Thanks,
>> Scott
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>