Hm… how about allowing to acquire locks within a transaction and just releasing locks on transaction commit? It won’t break current compatibility because we simply do not allow acquiring locks within transactions right now. I am wrong?
D. On Mon, Feb 8, 2016 at 4:10 AM, Alexey Goncharuk <alexey.goncha...@gmail.com > wrote: > 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. >
