Currently lock-only functionality is exposed via j.u.c.Lock interface on IgniteCache. We have two choices here: * Release such locks on transaction commit, which would break the contract of j.u.c.Lock * Do not release such locks on transaction commit, which, in my opinion, conflicts with the expectation of transaction locks.
Either way looks dirty to me, so I would vote for adding a new properly-named method on IgniteCache specifically for this case.
