Message Title

Andrea Boriero Yes, I did list that as an option but as I started playing with this I realized a problem with that - we do not always know the complete boundary of that call.

I thought of another option (hack?) where the Session itself could act as the CacheTransactionContext if there is not one, something like:

class SessionImpl ... implements CacheTransactionContext, ... {
    ...

    @Override
    public CacheTransactionContext getCurrentCacheTransactionContext() {
        return explicitCacheTransactionContext != null
                ? explicitCacheTransactionContext
                : this;
    }

    @Override
    public long getCurrentTransactionStartTimestamp() {
        // this is the single required method of CacheTransactionContext
        //        in this use case, the timestamp of the last explicitly joined/started transaction
        //        (or the Session start timestamp if one never explicitly joined/started) is fine
        return lastTransactionJoinTimestamp;
    }

    ...
}