SpringTransactionManager and UserTransactionImpl stored a reference to the TransactionManager which was no longer valid after a master-switch, now the tx-manager is looked up in the GraphDatabaseAPI for all operations. NOTE: The API of UserTransactionImpl changed, it takes a GraphDatabaseAPI constructor parameter again (was changed in 1.7 to javax.transaction.TransactionManager).
The change to a streaming approach caused the exceptions from cypher (due to the lazy nature) only to occur during the iteration of the result which as too late, so the Exception was not converted into a BadInputException but Internal Server Error Change contains a ExceptionHandlingIterable which allows to intercept and convert exceptions thrown during iterator(), next(), hasNext() and remove(). A custom implementation for REST Representation then converts Exceptions into BadInputExceptions.
…f URI creation
… care of that, all representations were changed to produce their data lazily in a streaming manner
…rting the revert. Revert "This introduced problems. Reverting it so that it can be fixed and pushed" This reverts commit 9942a0d.
…shed later. Revert "Added CREATE, DELETE, SET, FOREACH and WITH to Cypher" This reverts commit 7fb0603.
Added CREATE, DELETE, SET, FOREACH and WITH to Cypher
… killing the process as well as throwing exception
…fail sometimes on Windows
Method for instantiating a RelationshipTypeCreator so that it can be ove...
Added upgrade notes for 1.7
Bug when aggregation is used in order by and not listed in the RETURN clause
Changed the precedence of AND/OR