There was only a limited amount of design discussion that I am able to find around the relatively new listener methods added to AbstractThreadedTransaction/AbstractTransaction classes by TINKERPOP3-765 - that was also listed as "breaking", which, indeed, it is.
Can someone (Stephen?) post more information about the thoughts behind this design ? Matthias expressed unaddressed concerns: *http://tinyurl.com/omuz49e <http://tinyurl.com/omuz49e> * The Jira says very little about "why" this particular design was selected. I have similar concerns as Matthias. The design feels overly complicated and actually backwards from the way I was thinking about it. None of these things were required to get events out of Titan for the draft Kafka provider - so what is the value ? I believe the design expectation is that an Implementer, when creating a transaction object, will register an "EventListener" with the transaction, and then when the transaction completes, the appropriate EventListener methods will be called ? Even if that is correct, why so many methods on Transaction ? Thank you,
