Re: [Neo4j] WADL specification is the complete reference for all HTTP interactions with Neo4j?
Johnny, at which URI si the WADL hosted? Would like to look at the code, or you could dig into the code yourself if you don't want to wait. Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer brew install neo4j neo4j start heroku addons:add neo4j On Thu, Dec 1, 2011 at 1:28 AM, yobi johnny@yobistore.com wrote: I have noticed that you provide a runtime generated WADL specification for the HTTP API. I'm going to create a WADL to Node.js SDK converter so I don't have to create the functionality and change things manually each time you have a new release with changes to the HTTP API. a But before I do that I wanna be sure that this WADL specification is always an _up to date_ spec for _all_ HTTP interactions. Could someone confirm this? -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/WADL-specification-is-the-complete-reference-for-all-HTTP-interactions-with-Neo4j-tp3550226p3550226.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] WADL specification is the complete reference for all HTTP interactions with Neo4j?
The WADL is generated by Jersey which uses the metadata that it generates from the annotated REST-Endpoints. So it is always up to date: http://localhost:7474/db/data/application.wadl The Neo4j REST API is designed with discoverability in mind, so that you can start with a GET / and from there discover URIs to do other stuff. Examples below uses URIs for examples; they are subject to change in the future, so for future-proofness discover URIs where possible, instead of relying on current layout. The default representation is json, both for responses and for data sent with POST/PUT requests. Below follows a listing of ways to interact with the REST API. You can also see a (at runtime) generated description of the API be pointing your browser to the (exact URI may vary)http://localhost:7474/db/data/application.wadl To interact with the JSON interface you must explicitly set request header Accept:application/json for those requests that responds with data. You should also set header Content-Type:application/json if your request sends data, for example when you're creating a relationship. Am 02.12.2011 um 11:49 schrieb Peter Neubauer: Johnny, at which URI si the WADL hosted? Would like to look at the code, or you could dig into the code yourself if you don't want to wait. Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer brew install neo4j neo4j start heroku addons:add neo4j On Thu, Dec 1, 2011 at 1:28 AM, yobi johnny@yobistore.com wrote: I have noticed that you provide a runtime generated WADL specification for the HTTP API. I'm going to create a WADL to Node.js SDK converter so I don't have to create the functionality and change things manually each time you have a new release with changes to the HTTP API. a But before I do that I wanna be sure that this WADL specification is always an _up to date_ spec for _all_ HTTP interactions. Could someone confirm this? -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/WADL-specification-is-the-complete-reference-for-all-HTTP-interactions-with-Neo4j-tp3550226p3550226.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] WADL specification is the complete reference for all HTTP interactions with Neo4j?
How about extensions and plugins? Are these discovered by Jetty also? Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer brew install neo4j neo4j start heroku addons:add neo4j On Fri, Dec 2, 2011 at 11:55 AM, Michael Hunger michael.hun...@neotechnology.com wrote: http://localhost:7474/db/data/application.wadl ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
[Neo4j] WADL specification is the complete reference for all HTTP interactions with Neo4j?
I have noticed that you provide a runtime generated WADL specification for the HTTP API. I'm going to create a WADL to Node.js SDK converter so I don't have to create the functionality and change things manually each time you have a new release with changes to the HTTP API. a But before I do that I wanna be sure that this WADL specification is always an _up to date_ spec for _all_ HTTP interactions. Could someone confirm this? -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/WADL-specification-is-the-complete-reference-for-all-HTTP-interactions-with-Neo4j-tp3550226p3550226.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
