…it somehow, because I was running java8, which has a default implementation for the Iterator.remove method.
…ll do our dev work on the xn-blueprint branch. This will allow us to submit pull-requests to/from the original Tinkerpop repo.
…ance improvement for libraries that use Blueprints - Instead of wrapping elements as RawElement->Neo4j2Element->LibrarySpecificElement, we can do RawElement->LibrarySpecificElement directly, and improve memory usage. As part of this commit, some additional cast operations were removed (to, hopefully shave a few more milliseconds). NOTE: The code passes the test suite, but still needs some minor cleanup.
… class, that can easily be replaced later.
…s. NOTE: For now, the new implementations are not used by other classes yet.
…tion. NOTE: Not tested yet.
…raph is being initialized. This would cause problems if my first operation happened to be rolled back.
…tructors of Neo4j2Graph.
Since the Neo4j API has changed substantially this involved some significant modifications. The major one is that `setCheckElementsInTransaction` is now a (deprecated) no-op, since it no longer appears possible to determine in a straightforward manner whether a node or relationship has been deleted in a given transaction. The good news is that the consistency between the graph and legacy index data seems to have been improved, so the indices no longer seem to return deleted nodes/rels. **Note the following _breaking_ API change:** The `nodeIsDeleted` and `relationshipIsDeleted` **public** methods on the graph have been actually removed, since: 1. I can't figure out how to implement them 2. They were only used (internally) for checking if elements were in a transaction, which is no longer required 3. It's better that people fix code to not depend on these methods than for them to do something wrong/misleading/throw an exception Additionally, fixed various test code. A note on compatibility: I've tested this on a reasonably substantial project and the only differences I noticed from 2.1.x involved order of relationship iteration, which shouldn't be depended on anyway.