Hi guys,

we are experimenting with setting up neo4j in our application. our current 
approach is to initialise a GraphDatabaseService (because we thought that 
this might be the fastest way to access the db) and utilise the 
(deprecated) WrappingNeoServerBootstrapper to encapsulate it in a neo4j 
server to allow the access to the db via the web interface. thereby, the 
problem is that neo4j server (2.0.0-M06) depends on jersey 1.9 and our 
application makes use of jersey 2.x. so we are running in a dependency 
problem between jersey 1.x and jersey 2.x (currently, it's mainly the 
Response class of the jax rs interface - a similar problem is also 
described at 
http://jersey.576304.n2.nabble.com/Repackaging-Jersey-1-x-jars-without-jax-rs-td7580810.html).
so are there any plans to migrate neo4j server to jersey 2.x?
Our next plans are to check out the rest interface so that we can run the 
neo4j db as standalone service. are there any benchmarks/comparisons 
between the both apis (the native java api and the rest api)?

thanks a lot in advance.

cheers,


Bo  

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to