Expose the curTransaction thread variable

[Sridhar Ramachandran]

(Request from user)

"With Blueprints' automatic beginning of transactions, it is easy for a user to not realize that a transaction has been started on his behalf. This in turn makes it easy for transactions to leak. In a general application context where thread pools are commonly used this can cause all sorts of bugs. "

[Sridhar Ramachandran]

BitsyGraph has a new isTransactionActive() method.

Changes: - https://bitbucket.org/lambdazen/bitsy/commits/fff149425f395239b1aae679768aa8e4c6a0a2db - https://bitbucket.org/lambdazen/bitsy/commits/68cb7ebcbe9d7e5cc8f7548a065bc2e22fa20f8e

[Sridhar Ramachandran]

Related to feature request at https://github.com/tinkerpop/blueprints/issues/435

[Pieter Martin]

Hi,

Can you please add the isTransactionActive() method to BitsyAutoReloadingGraph.

Thanks Pieter

[Sridhar Ramachandran]

Sorry about that. The method is now in BitsyAutoReloadingGraph as well. There are also some basic tests to make sure that it works on all three graph types.

LInk to code changes

The 1.2 snapshot in Maven should have the fix. Please let me know if you still have problems.