Currently, transaction is wrapped around a single run block. Typically, there is a begin transaction & commit semantic where we can get a tx ID and tie operation to the tx ID. According to @vkedia, there is the wire protocol for this, that can be exposed. This could help significantly in tying better w/ JTA standards.
Currently, the community jdbc driver is trying to work around this by having a single runnable thread that listens/pulls from a queue of requests.
/cc @emmanuelbernard to see if this will be helpful & what the JTA needs are.
Currently, transaction is wrapped around a single run block. Typically, there is a begin transaction & commit semantic where we can get a tx ID and tie operation to the tx ID. According to @vkedia, there is the wire protocol for this, that can be exposed. This could help significantly in tying better w/ JTA standards.
Currently, the community jdbc driver is trying to work around this by having a single runnable thread that listens/pulls from a queue of requests.
/cc @emmanuelbernard to see if this will be helpful & what the JTA needs are.