could you please uograde the jersey-client version about java-rest-binding

[mangrish]

I totally agree. Right now I'm running embedded because jersey 1.x dependencies are killing my project.

I forked the repo and tried to superficially upgrade the jersey version in the 2.0 branch (https://github.com/inner-loop/java-rest-binding/commit/3b6b4e06bc7205c651e15386d040cb8f0772ec56). My idea for testing was that since this is just an upgrade all existing tests should pass (regression) but for some reason the actual neo4j-server has a dependency on jersey 1.x as well so now every test fails with a NoClassDefException when trying to start a server (culprits are here: neo4j-server-2.0.1:org.neo4j.server.database.[InjectableProvider, DatabaseProvider, CypherExecuterProvider, GraphDatabaseServiceProvider]. More importantly the production server java for neo4j has a direct dependency on a REST api! Not sure why that has happened but there you go. If the requirement is still there to use the jersey dependency injection it might be worth moving that code to this project and link it up with the hk DI.

If @jexp can advise on what to do next that would be awesome.

Speaking of which what is the state of this branch? is it still being actively developed?

[jexp]

The problem is, that for testing we have to stick with the jersey library of the server. Which is now at 1.9 Otherwise it blows up with incompatible versions.

I recommend anyway to rather use the Neo4j jdbc-driver these days. Java REST binding builds upon a broken abstraction: https://github.com/neo4j-contrib/neo4j-jdbc

[mangrish]

I 'm (and I assume many others) using the Spring Data for Neo4J libraries (https://github.com/spring-projects/spring-data-neo4j). What is the approach around getting these to work?

Also will projects like Graphene support this new jdbc driver type approach?