Re: [windup-dev] REST <- graph api?

+1 to getting this straight before getting deep into Windup 3. To those 4 approaches in the document, I would suggest one more. Kind of a hybrid. The point of this, I assume, is to reduce the repetitive patterns in the chain: graph -> Java Model -> Java service -> DTO -> REST -> JSON -> TS service -> JS model -> Angular 2. So we should reuse the information already contained somewhere. The most frequent scenarios I can forsee are: 1) Query by property, get the resulting objects, optionally with some nested objects. 2) Start with a set of objects, query some other objects in some relation to those. 3) Start with one object and get a tree starting with that object, based on some recursive relation. 4) More complex queries. I suggest to stick with something simple, so for 4), we could have custom services. For 1) 2) 3), we could have a simple "URL to objects" schema, not trying to be a generic query tool. It could reuse the Models. Examples (made up): 1) /graph/File{path=...}!out:fileToProject,getClassifications,:... -- File objects with given properties with objects from relations defined behind ! attached to it. 2) /graph/Project/id=[1,2,3]/out:projectToFile/{path=...} 3a) /graph/Project/id=1//in:parent!out:fileToProject -- will query what's under that relation 3b) /graph/Project/id=1//in:parent!getProjects -- will use the method to attach the objects. Maybe it's quite similar to what's proposed in the doc under 4, only a bit more type oriented, and also more use-case oriented and less generic. my2c. Ondra On 1.7.2016 23:28, Jess Sightler wrote: