users@jta-spec.java.net

[jta-spec users] Re: rough draft of JTA 1.2 section 3.8 TransactionScoped Annotation

From: Paul Robinson <paul.robinson_at_redhat.com>
Date: Wed, 28 Nov 2012 09:21:02 +0000

>>
>> 3) Is it felt necessary to address the behaviour of scopes in distributed (i.e. multi-JVM) transactions? This is not the case for TSR get/put behaviour for example, with most implementations opting to consider the TSR storage to be node local, hence not allowing a put in one container to be visible to a get in anther container, even if the logical transaction context is equivalent. I think it's reasonable for scopes to behave likewise, but do we want to enforce that they should (or should not)?
>
> I agree that it's reasonable for scopes to be node-local. However, I seem to remember that CDI scopes, and the associated bean instances, can span multiple JVMs. I'm struggling to find a reference to this so I may have misunderstood.

Ignore the above statement, I managed to hit "send" rather than "save draft" :-(

-- 
Paul Robinson
Web Service Transactions Lead
paul.robinson_at_redhat.com
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)