Distributed transactions and synchronization
By default Infinispan registers itself as a first class participant in distributed transactions through XAResource. There are situations where Infinispan is not required to be a participant in the transaction, but only to be notified by its lifecycle (prepare, complete): e.g. in the case Infinispan is used as a 2nd level cache in Hiberenate. Starting with 5.0Â release, Infinispan allows transaction enlistment through Synchronisation