Hi Michael, Thanks for the reply. I should have included that information...
We have maven dependencies on neo4j-enterprise, neo4j-ha, neo4j-cypher and neo4j-server. We also have an additional dependency to deploy the static-web files of neo4j-server. Our goal is to have neo4j running 100% embedded (accessed with Java API) within our WAR, but we also desperately need the webadmin tool for debugging. When we try to pull in Jersey 2.x, it conflicts with the Jersey dependencies (jersey-core specifically) referenced from neo4j-server. Once I exclude Jersey dependencies from neo4j-server the webadmin tool breaks (the embedded DB works fine). Perhaps is there a way for us to have the webadmin tool without pulling in neo4j-server and/or Jersey? Much appreciated, Thanks On Monday, September 15, 2014 12:24:00 PM UTC-4, Andrew Stone wrote: > > Hello, > > We are running neo4j embedded within our application and have the need to > include a module which depends on Jersey 2.9 / JAX-RS2.0 > > Neo4j-server is running Jersey 1.9. > > As you may know. v1 and v2 of JAX-RS API have fundamental differences that > do not allow them to execute within the same classpath. So we are stuck and > need to either downgrade the other module (we own it) or try to isolate it > within its own classpath - either adds additional overhead for development. > > *Does Neo4j have any intent to upgrade their Jersey version? Has anyone > else run into this problem? What was your solution?* > > > Thanks > -- 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.
