No, I don't want to add it back since example does not work. Val, I have just very thoroughly rechecked this and it seems you are far from being right.
I see that connection used in ignite store listener and connection (and, moreover, sometimes 2 connections - in case of update-insert sequence) used by jdbc template are different. And each connection gets requested and closed by jdbc template on per operation basis. All you talk about can be achieved with explicitly configured tx manager. I don't want to do it since it is 100% overkill for this example. So, I prefer not to add it back - we have 2 store examples more. --Yakov 2015-12-17 11:22 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > Can we please add this example back? > > On Wed, Dec 16, 2015 at 10:45 PM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Yakov, > > > > Code in Spring example was not ignoring txs. There > > was CacheJdbcStoreSessionListener which handles this automatically. > That's > > how Spring works - it enlists all calls to jdbcTemplate into transaction > if > > it was opened by tx manager in this thread. > > > > -Val >
