> [...] , but I don't understand why the fact that it's
running on a different process is limiting in any form.

You are correct, it is not limiting.   XA is process locality independent.   Individual TXN participants (heterogeneous or homogeneous) register as XA resources (via JTA) with a central TM (which, if JTS compliant, supports XA).  The TM then basically implements a classic 2PC to bound the scope of the TXN processing and outcome.  An example of an XA transaction with heterogeneous participants could be a database (viewed by the TM as a resource=javax.sql.XADataSource) and a Queue (viewed by the TM as resource=javax.jms.XAQueueConnection). 

BTW, though not done in the JCache 1.0 draft, an ideal Java API in support of Cache as XA participant will be realized when JSR-107 provides something like a javax.cache.XACacheSource.

---

View this message in context: Re: [infinispan-dev] CacheStore redesign: no XA cache stores
Sent from the Infinispan Developer List mailing list archive at Nabble.com.