they will be added in Infinispan 9.0 (due in the autumn).
However you can use scripts and tasks now to implemented "stored procedures" which run on the server and have access to the full embedded API, including transactions.
Thanks for the update Tristan. From a Java EE 7 client's perspective does this mean JCache operations in a remote server configuration will be transactional? Right now I have an application running in WildFly with a embedded Infinispan configuration. If I change to a remote Infinispan configuration with Hot Rod transactions will the client application behave the same as before?
Well, since JCache 1.0 doesn't mention transactions anywhere this behaviour is undefined. I guess you'd want the HotRod client to participate in an XA transaction ?
Ah ... so it's quite possible that the transactional behavior isn't even working the way I assume it to be in embedded mode with JCache? Right?
It all depends on what you want to do and what you expect
Bear in mind that not only doesn't the JCache spec say what the behaviour should be with transactions, it doesn't even specify what the behaviour should be in a cluster.
So, if you're talking about put, gets, removes, you should be fine, but for things like entry processors and readers and writers each implementation might behave differently.
Unfortunately it wasn't introduced in time. The protocol and the server are updated to handle the transaction but none of the clients were updated on time.
It will be supported in the next version.