The Weaver code has been thrashed around quite a bit -- I was learning/discovering various Gremlin techniques along the way. Overall, the code could use some significant refactoring.
Additionally, the queries within a transaction should be more accessible, and we should have more control over the variables and variable names within a transaction.
The Weaver code has been thrashed around quite a bit -- I was learning/discovering various Gremlin techniques along the way. Overall, the code could use some significant refactoring.
The latest refactoring change was to add WeaverInstance as a starting point (with configuration settings for each instance).
At the least, I think that WeaverInstance should absorb the static WeaverTasks class.
Additionally, the queries within a transaction should be more accessible, and we should have more control over the variables and variable names within a transaction.